Property update on release

[jason.dupree]

Since the titleblock tags do not reflect on the drawing itself, utilizing the PLM_Properties seems like a better solution except that they don't update as the Items are released, meaning any properties that change on release (like Major and Minor Rev) won't reflect on the released drawing.

The idea here is to either have the Update primitive either automatically or have an option to update the drawing with the latest properties after the release happens. Even if there were a primitive that did just this and it could be put after the Update primitive, that would work as well.

[arnau_llovet_vidal]

When you have and item with revision number, this number is not stablished in upchain until it's released.

This creates problems when creating drawing that reads item revision information from upchain, because the updated information is not available.

Example:

You have a released item let's say A-00 revision

You set the item in development, the index stays in A-00

Usually you edit your drawings while your item is in development, if you link some text with the attribute Item Revision it is set as A-00 (This is a problem, you are making the new index B-00 or whatever drawing, and upchain sets the old index)

You release your item and drawing

The item now is in release status and the revision changes to B-00 (or A-01 or whatever you have set as revision)

The drawing is released with A-00, and the index information is not updated and in consequence is wrong.

It would be much more practical to increase the revision information while the item is in development. This way it would be much easier to identify that you are working in the new revision, and not the old (which is already released!)

[andreja.schneider]

Hi @jason.dupree,

thanks for posting this idea! Could you provide us with information if you could benefit from attributes being populated on the pdf instead of on the drawing? Currently we are legally bound and prohibited from using external CAD software for population of PLM attributes on file properties and that prohibits work executed on the primitive. 

Best regards,

Andreja Schneider

[arnau_llovet_vidal]

This is exactly same Idea as we posted some days ago

https://forums.autodesk.com/t5/upchain-ideas/set-item-the-new-revision-when-the-item-is-set-to-devel...

[rich_walters]

I was disappointed to find this out that Upchain Attribute Codes cannot be added to BOM tables in Solidworks drawings and really surprised about the legal limitations. PLM attributes can be added in BOM tables but not Upchain Attribute codes. Because revisions are updated upon release, using PLM revision attribute is always one behind unless already released. This is a problem when child parts are being revised at the same time as the parent. 

It would be great if there was an option to populate the Revision column in the table upon release. How is this different that using the codes in the revision table? We need the child revisions too. As others have stated, allow the user to set the future revision in the item that is in development is a good idea too.  

[oleksandrQ7M6R]

I tried everything to implement this on drawings.

The first approach of increasing the revision when an item goes into development doesnt work when you have options of minor and major revisions.

Using curly codes only looks at the item level and applies the assembly revision to every item in the BOM table on the drawing. The only way this works if there is a post SW engine that would open the drawings keep all the formatting and regenerate the PDF after release. 

[nicolas.letourneau]

I have the same issue when I'm trying to write the major revision item attribute to Inventor iProperty "Revision Number". The item attribute is written when the part status changes to "Development" but the major revision changes when the part status changes to "Released". As a result, the "Revision Number" from the part iProperty is always one incrementation behind.