Deleted everything.
Imported eveything.
Worked flawlessly in the new company.
Great program!!!
I love it!!!
Thank you!!!
Richard
2 Likes
Probably just had to add the other company to the security in the function library.
Wait until you see what’s next..
5 Likes
I’m late to the party here, but I just tried this out and LOVE it! Thank you @klincecum!!! 
This makes refreshing a Pilot db that users are still testing in so, so, much easier.
Has anyone tried exporting BOOs/BOMs? We often have people trying out new manufacturing routings in Pilot db, and when they’re happy with the new routing, they have to copy/paste them into the Live db.
@klincecum , can I export myself?
1 Like
Exporting BOM data is straightforward. The table you export from is PartMtl, and the DMT upload is “Bill of Materials”. All the fields in PartMtl are in the DMT upload, AND you need both a “Plant” and “ECOGroupID” field for the DMT upload.
BOO data is a little more complicated. There are two linked tables, PartOpr and PartOpDtl (the second table holds the ResourceGroup/Resource/Capability capacity constraint). The DMT upload is “Bill of Operations”, and also requires a Plant and an ECOGroupID.
The way the DMT works for this is literally the same way you’d add (or modify) a Part Revision record through the user interface. Each line in the DMT upload essentially checks out the Part Revision to the Engineering Workbench (which is why you need the ECOGroupID field), makes the change, and then approves and checks the part revision back in.
These are NOT fast DMT uploads. Your RPM (records per minute) will almost certainly be below 100, and depending on complexity, maybe even less than 50. Do it in small chunks… error message tend to be, shall we say, not incredibly helpful.