Issue (Bug) with data loading of Documents

[avillanueva]

I came across and issue that I think should be shared.  I will confirm this and have opened a ticket on this.  I am loading Parts, Docs, Links and content. The order I had was load Parts, Load doc objects (empty), load links (part to doc and doc to doc) then load content.  Some loaders create iterations, others do not.  When the content loader ran (just another BeginWTDocument but now with content), iterates document to add content but does not carry forward the links to that document.

Here is an example: Let's say Part A is described by doc B and Doc C references doc B.  On the related objects page would see links to those other objects.  When the loader for the content runs, the document is iterate and those links are gone. If you go to previous iteration, they are there.  If you go to Part A or Doc C, the links are gone (since no longer latest).  However, if instead of loading content via XML I checked the document out and uploaded content manually, the links are carried forward. The gap is the loader was not ever programmed to carry forward links.  

I can change the order but I need to test first.  Something to watch out for.  I guess you might say why I am running create doc XML load and file content separately. Yes, they can be loaded together but it was way more complicated.  I can load docs successfully, links then content was the plan.  Small moves Ellie.  Combining made a complicated load file.  

I will run a test and report back.

[avillanueva · Accepted solution]

Confirmed. Order is important.  I ran one load file to create the document and push meta data:

<?xml version="1.0" ?><!DOCTYPE NmLoader SYSTEM "standardX20.dtd">
<NmLoader>
<csvBeginWTDocument handler="wt.doc.LoadDoc.beginCreateWTDocument" >
<csvname>OBSOLETE: MANAGEMENT RESPONSIBILITY</csvname>
<csvtitle></csvtitle>
<csvnumber>LoadOrderTestDoc</csvnumber>
<csvtype>Document</csvtype>
<csvdescription></csvdescription>
<csvdepartment>DESIGN</csvdepartment>
<csvsaveIn>/Default</csvsaveIn>
<csvteamTemplate></csvteamTemplate>

Then I ran same thing with no meta data but with content:

<?xml version="1.0" ?><!DOCTYPE NmLoader SYSTEM "standardX20.dtd">
<NmLoader>
<csvBeginWTDocument handler="wt.doc.LoadDoc.beginCreateWTDocument" >
<csvname></csvname>
<csvtitle></csvtitle>
<csvnumber>LoadOrderTestDoc</csvnumber>
<csvtype>Document</csvtype>
<csvdescription></csvdescription>
<csvdepartment>DESIGN</csvdepartment>
<csvsaveIn>/Default</csvsaveIn>
<csvteamTemplate></csvteamTemplate>
<csvdomain></csvdomain>
<csvlifecycletemplate></csvlifecycletemplate>
<csvlifecyclestate></csvlifecyclestate>
<csvtypedef></csvtypedef>
<csvversion>C</csvversion>
<csviteration></csviteration>
</csvBeginWTDocument>

<csvEndWTDocument handler="wt.doc.LoadDoc.endCreateWTDocument" >
<csvprimarycontenttype>ApplicationData</csvprimarycontenttype>
<csvpath>/pdmlink/ptc/Windchill/loadFiles/Agile/Agile/371963/01_2001.DOC</csvpath>
<csvformat></csvformat>
<csvcontdesc></csvcontdesc>
<csvparentContainerPath></csvparentContainerPath>
</csvEndWTDocument>

Then I ran the other load methods that created links.  No issue in that order.