Thanks for your reply.
We store the drawing on the Part record as attachment. We only want the latest revision attached. When we attach we only use the drawing number in the filename (no revision) and it is a visualization file. We run a nightly automated task that copies latest CAD visualization files to the repository that holds our Epicor attachments. We use AutoCad vault for the checking in and out of the drawing and the automatic creation of the visualization file when the drawing gets checked in.
With this method, when a drawing gets bumped up a revision and checked in, Epicor automatically has the most recent approved drawing attached the next day. However, the part revision in Epicor now needs to get bumped up. If a user gets a drawing and the revisions do not match, there is concern about whether it is the latest approved drawing, whether it is the correct drawing (eg sometimes people duplicate parts and forget to remove attached drawing that is not correct) or if something went wrong with nightly automated task… We also have some pdfs of old drawn files attached, and have need for those revisions to jive with Epicor part revision as well. These are few and far between.
It certainly would be easier if the Epicor part revision did not need to match the latest approved drawing revision, but I don’t think the people here will go for that since it has occasionally shown to be erroneous.
Since my original post I’ve been toying with using a DMT w PS script to pull the data (via BAQ export in DMT) and then load it back up via DMT with new rev. It feels a bit brute force, but I think maybe if it can get running smoothly then it could be a viable option. We hope to upgrade within next two years. I’d think that a DMT and PS method should stay feasible…
Please continue to let me know your thoughts and ideas.