Hey BJ! Long time no hear from ya. Welcome back!
I just happened to be using the webtools earlier this week and I can confirm that is the way they are sorted and that it would probably be better to sort these by createdStamp before writing the export file instead of what I believe is the normal indexing by primary key. I was going to create a JIRA issue as soon as I created a patch, but feel free. The write order could be more intelligent, but I think the sort by createdStamp will handle many of the situations without putting too much additional thought behind it. --- BJ Freeman <[EMAIL PROTECTED]> wrote: > I search the Jira but asking here in case I missed something. > when a complete entity export is done.The dependent entities are not > sorted so > they are import after the parent Id are. I am not sure at this point > if it is > entity specific. > example > <PartyType partyTypeId="Fullfilment" parentTypeId="Suppliers" > lastUpdatedStamp="2006-06-18 02:50:03.697" > lastUpdatedTxStamp="2006-06-18 > 02:50:03.587" createdStamp="2006-04-10 14:21:32.027" > createdTxStamp="2006-04-10 > 14:21:32.027"/> > > is before > <PartyType partyTypeId="Suppliers" hasTable="Y" > lastUpdatedStamp="2006-06-18 02:50:03.737" > lastUpdatedTxStamp="2006-06-18 > 02:50:03.587" createdStamp="2006-04-10 14:19:13.297" > createdTxStamp="2006-04-10 > 14:19:13.297"/> > > so when it imports, there is a error and and the import for the file > is rolled back >
