Has this process changed with the 2010 beta? I found the instructions in the Admin Guide and followed them to the letter, but nothing shows up in my drawing card. Actually, two of the fields populate, one with the correct value and another with weird data from some unknown source.
The field that populates correctly does not include the $PRPSHEET attribute that the Admin Guide says is needed. The field for which I created that attribute gives me nothing.
What the ???
I've attached an image of the mapping I'm using. I created the $PRPSHEET mapping for the slddrw extension and removed the slddrw extension from the CustomProperty mapping. Is this not correct?
The Revision property of the Part file comes through in its file card, but I just can't get it to propagate over to the card for the dwg. Most puzzling.
PS, I do have the Revision variable attached to the text control on both data cards...
After more research, it seems the problem was that I didn't have the EPDM Add-In running (the Admin Guide does explicitly mention that this is necessary, but I had apparently glossed over that part).
The strange thing is that once I change the value in the part card, it won't update in the drawing card until I
This is not only a pain, but also causes versioning of the drawing, which I would like to avoid unless absolutely necessary.
One interesting point: With the draw card updating from the part custom property in this way, I notice that when I open the drawing, it is immediately flagged as having been modified, even before I do anything to it. Presumably that's because it has 'modified' itself by updating to the custom property of the part.
It's by design. EPDM can't update a card for a file while the file is checked in. Also, the file needs to be versioned because, well, it is a new version because something changed with the file.
Something to keep in mind; if a file is checked out, and there hasn't been a modification done to it, the system performs a 'Undo Checkout' on the file. I ran into that little gotcha a few times when getting started.
Sounds like an interesting solution, Wayne. Unfortunately I'm not an Add-in programmer and I don't think such a program is publicly available. Worth keeping in mind, though.
Retrieving data ...