At a minimum EPDM should alert you that it is going to do an undo check-out and give us the opportunity to accept or check-in.
I understand it is trying to save us versions and space but we have run into a couple of instances that it did an undo check-out to a file and there was indeed a change made to it.
You could make a change to the data card, hit save on the card, then change the card back and re-save the card. That will trick PDM into thinking the file has changed.
This is a question I've faced before. For clarification, you really aren't interested in the undo checkout/force check in, right?
Conversely, you need functionality to catch when files are renamed and update the "drawing number" and "part number" datacard fields to the new name, right? I have an add-in that runs on a file rename that scans the datacard for the fields to update it to the new filename...or something along those lines.
PM me if interested in a quote.
Hi Brian, I assume on your data cards certain variables are set as special values (ie read from file name) for part number etc? My suspicion is that these values are only assigned once, and cannot be dynamically updated unless you have a dispatch action or something like that running. So when you first add a file to the vault, your data card is correct, but when you then change the name of the file, the values will not change and hence PDM thinks no change has been made to the file.