I am attempting to perform a data migration for a specific list of projects, but for some reason the read is only pulling the first two projects in my list. The projects exist in the system I am reading from and it gets the first two in my list, but nothing after that. Any help would be greatly appreciated.
Here is what my read looks like:
<?xml version="1.0" encoding="UTF-8"?>
<NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_read.xsd">
<Header version="6.0.11" action="read" objectType="project" externalSource="NIKU">
<!-- you change the order by simply swap 1 and 2 number in the name attribute -->
<args name="order_by_1" value="name"/>
<args name="order_by_2" value="projectID"/>
<args name="include_tasks" value="true"/>
<args name="include_dependencies" value="true"/>
<args name="include_subprojects" value="true"/>
<args name="include_resources" value="true"/>
<args name="include_baselines" value="true"/>
<args name="include_allocations" value="true"/>
<args name="include_estimates" value="true"/>
<args name="include_actuals" value="true"/>
<args name="include_custom" value="true"/>
<args name="include_burdening" value="false"/>
<Filter name="projectID" criteria="OR">*03652, *10439, *09649, *09651, *096714, *11076, *08403, *09775, *09645, *09648, *09652, *09646, *09650, *08493, *11363, *09811, *08912</Filter>
Don't think you can "wildcard" like that in the OR list ; has to be specific (full) IDs.
(assuming that you are trying to wildcard with those *s)
If the wildcards didn't work then why would it have grabbed two of the projects and nothing else? The naming convention is PRJ-#####, but we've had issues with the '-' being used as an operator in the past.
Don't really know - I'm just GUESSING based on vague recollections. XOG is a little idiosyncratic I find!
Some discussion here - RE: XOG out filtering with "starts with" criteria? but not related to project reads.
According to this
Learn PPM with Rego: XOG, Gel Script Save, Rate Matrix with MSP, Duration, Java 8, and a 10 ALPHA Character Grab
wild cards should work to some extend.
Would an inactive project not read?
It would read inactive as well
This is still a huge issue for me and I now have to read several hundred projects. No one has seen this before?
Unmarking as Assumed Answered in hopes you get more feedback.
Assuming that you are using v14(from the header version), there is a new functionality introduced called pagination. Basically there is a XML governor limit being applied when you do mass xogout to tackle the OOM scenarios.
Ideally you should not be hitting the governor limit for just 2 projects.
To confirm this, can you please paste the tail of the XOG output. If you are seeing a Skip Value in the Xog output tag, then you are hitting the limit.
I'm actually trying to read from version 220.127.116.116 and writing to v14. We had to work around the previous attempt by doing them individually, but now I have to do it with several hundred and that is not an option. The XOG output this time around isn't even putting a Skip value:
<Statistics failureRecords="0" insertedRecords="0" totalNumberOfRecords="1" updatedRecords="0"/>
When I ran into this issue before it did give us a filtered records number.
The exact same filter that is being used for this project read is being used successfully for Costplans, benefits, issues, risks, changes, and budgets.
Is there anything that can be done or am I just out of luck?
While scrolling back to the first message in this thread, I am seeing the xogout results which has the skip value in it as skip value =2
If you are reading from v13.3, you should not be seeing the skip value.
Can you confirm if you are facing the issue of only 2 projects being xogged out in 13.3 as well?
In v14, this behaviour is expected.
In my most recent read(of 166) from 13.3, I'm seeing no skip values, but it's only reading 1.
Try the XOG Bridge from ITROI (solutions)
That is not an option in this situation.
Hi Tony.Roth - Did Adersh's response help answer your question? If so please mark as Correct Answer. Thanks!
I didn't tried with wildcard filtration but just a thought, i can see spaces between the project id and comma in your filter condition. Did you tried after removing the spaces?
Alternative solution, Filter the record using any other attribute which will be common for all those projects. It can work even if it is custom attribute as well.
In order to filter using Custom attribute, you can use below syntax
<FilterByCustomInfo name="ATTRIBUTE_ID" criteria="BETWEEN">2012-12-1,2012-12-23</FilterByCustomInfo>
Do let me know if you face any issue.