Skip to main content
Feb 6, 2024 5:00 PM UTC
Acknowledged

Allow part and (sub)assembly parameters in a 3D Note as are allowed for bulk items

Related products:Creo Parametric

Please include detailed documentation such as screenshots, images or video.

1. What product and version are you running?
Creo Parametric 9.0.4.0


2. What is the problem?

Part or (sub)assembly parameters cannot be referenced in a 3D note at the assembly level.  This behavior appears inconsistent because bulk item parameters can be referenced in 3D notes at the assembly level.  The parameters for a bulk item can be reference at the assembly level 3D note using <parameter>:FID_# where # is the feature ID of the bulk item.   However, if a lower level "component" is a part or subassembly the above method does not work.  Nor does using <parameter>:SID# where SID# is the session ID allow the lower level parameter value to appear in the note.  


3. Are you using a workaround? If yes, please describe it.
There is a work around in that in Relations one can create a parameter <parameter_test> and declare it equal to the lower level parameter using <parameter>:SID# and then call the assembly parameter in the 3D note by using the "&"  (i.e. &parameter_test).  

4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.

The use case is with model based definition there is a need to call lower level parameters such as description, part number or general model information at a higher level to define the product.  This is indeed possible with bulk items and a workflow for calling parameters from those items is possible.  Having consistent behavior with parts and assemblies would allow for a standard workflow for assembly level 3D MBD notes.  The solution could uses the session ID instead of the feature ID like a bulk item.  The ask here is that it be possible to directly (and easily) reference the lower level part numbers without have to create a new relation for them.

5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)
The workaround is obviously more work and can make for the need of a lot of "unnecessary" relations in the assembly.  With model based definition, referring to lower level product information is becoming more common in a 3D note.  Hence each user will have to spend several more minutes creating relations where a consistent behavior would eliminate those minutes.  It doesn't sound like a lot, but over many assemblies the time adds up.

1 reply

Feb 7, 2024 7:28 AM UTC
Status changed to: Acknowledged

Hi @Thomas_Primosch!

Thank you for your idea. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.