When I try to use the "Set revision" command SW PDM does not give me the data card variable value as an option even though it sees what the current value is and that matches my revision scheme.
The workflow state needs to set the initial Revision to 1, whichever is first in the list. Try that on your initial state and see if it changes.
I tried what you suggested. Here is what my initial state looks.
Here is the preview tab of the file. Notice the data card revision has the desired value of 04. The local revision didn't get picked up on check in.
And in my set revision I don't get any available value besides 00, even if I have the local revision already set.
Are you trying to set the revision to a value that is on the data card?
If so, take a look at the attached video.
You can select and individual file and set the revision, or multi-select and set them all using the right-click option.
Hi Matt -
Maybe I'm misunderstanding what you are trying to do?
But, I would not change the initial state.
Back to my original question: Are you trying to set the revision to a value that is on the data card?
I would create a new transition from the initial state to the released state (Move Legacy) with no transition actions to simply move the documents to the state.
Then I would use the Set Revision command to set the revision (as shown in the video I posted earlier).
That is the way I have it set up. I had an initial state then made the transition and set the revision manually in the next state.
Maybe this is irrelevant, but I am on 2017 PDM Standard, not Professional.
AHA! very relevant - I should have asked.
So, I am assuming you are trying to put legacy documents into the vault at the released state?
In Standard, you cannot have two transitions between two states.
So, in order to handle legacy files, you can do something like this...(see attached video)
That doesn't seem to fix the issue. Here is what my workflow looks like.
The area to the left is where my legacy files are being circulated for import and revision capture for documents we have created. The rest will be the standard workflow these documents work through. The reason I need to set revision on some files is that we get drawings from manufacturers that have been revised by them and I need to set the revision to what it is when we receive the drawings. I only have a single revision component set up as below.
So my question is relative to this: The reason I need to set revision on some files is that we get drawings from manufacturers that have been revised by them and I need to set the revision to what it is when we receive the drawings.
When you receive these drawings, is there a custom property that is set to the revision value? And, does it match your revision scheme?
I don't understand the function and purpose of the check revision loop?
Perhaps it's best if you consult with your VAR.
Some of our OEMs use a number based system. In those cases, we start at whatever revision the drawing is at and continue forward. If an OEM doesn't use the same revision system we start from 00. These drawing are .dwg (the problem is the same on SW files also) and for the electrical of our manufacturing equipment. We have on-staff electricians that will make changes to the machines that need to be documented.
I have the revisioning loop on the left set up because while changing from PDMWorks to SW PDM (I am handling the migration manually) I need to retain the revision history of these drawings.
So, what is happening in this part? Does anything happen on the Incorrect Revision transition or Revision Updated transitions?
On "Incorrect Revision" it creates a new version and increments the revision. I record the changes in the drawings and check it back in with an overwrite revision. I then make the "Revision Updated" transition which has "Overwrite Latest Version" set. I have it set this way so we can view the past revisions and the Get Version flyout looks like this. It minimizes the versions being created while maintaining past history.
On drawings that don't start at 00 I don't want the extra versions so as to not cause any confusion. I just want to start at whichever revision the drawing is at when we received it. I can run it through the loop to get to the revision I want but I end up with all those extra revisions ending up in the flyout.
So, when the drawing is added to the vault, does the revision appear on the data card or are you writing it on the transition?
It gets pulled into the data card by a block in the drawings.
If all the files have a valid revision value on the data card, then all you need to do it get it to the proper state and set the revision as shown in my previous video. I'm back to the 'what am I missing' part?
If the data card was missing the value, then you would need to update the data card prior to set revision so that it would be set properly.
I'm with you. I found a workaround but it requires me to erase the regular part of my workflow because I need the extra states since I am limited to 10 by PDM Standard. I am creating a state for each possible revision that I need to immediately go to. In the transition to these states I am setting the revision. Tedious since I have to undo some work and redo after I am done importing but it will get the job done.
I would simply check out the file, set the revision, then use set revision.
I hate those Frankenstein workflows where you have a state and transition for every possible revision.
When I was a customer (pre - set revision function), I had an admin only transition where I would set the increment on the transition - tedious, but, at least I knew it was right).
Retrieving data ...