Hey Ricky. In this example, the cut part is going to to Inventory History as waste. But it keeps it's job #, instead of getting a job # "WASTE" like the drops from the cut lists. Would this be a regular use case? You won't be able to use the beam again in the system unless you make a new PO# for this item to be received to inventory. Probably with a lower unit price as it's the waste already accounted for in another project. Cheers. Igor Guerra
Ricky, if the XML import rejects the changes due to TFS status: does the drawing update and revision status update? Or does it reject all updates from the import for that TFS assembly ? Would it make sense to simply re-import the XML after doing the reverse TFS process?
I'd have to test to be sure, but I'm pretty sure it does actually bring in that drawing in spite of the TFS. But yes, you could just reimport after reversing the TFS.
Hey Ricky. In this example, the cut part is going to to Inventory History as waste. But it keeps it's job #, instead of getting a job # "WASTE" like the drops from the cut lists. Would this be a regular use case? You won't be able to use the beam again in the system unless you make a new PO# for this item to be received to inventory. Probably with a lower unit price as it's the waste already accounted for in another project. Cheers. Igor Guerra
Ricky, if the XML import rejects the changes due to TFS status: does the drawing update and revision status update? Or does it reject all updates from the import for that TFS assembly ? Would it make sense to simply re-import the XML after doing the reverse TFS process?
I'd have to test to be sure, but I'm pretty sure it does actually bring in that drawing in spite of the TFS. But yes, you could just reimport after reversing the TFS.