Skip to main content
Jul 21, 2025 6:45 AM UTC
Acknowledged

Improve Update Behavior for UDFs in Creo – Enable Auto-Update in Referencing Models

Related products:Creo Parametric

1. What version of the software are you running?

We are currently using Creo 7 and update to Creo 11 in August (Tests in Creo 11 have not shown any improvement)


2. What is the problem?

When a User Defined Feature (UDF) is updated (e.g. modified geometry, parameters, relations), the changes are not automatically reflected in models where the UDF has been previously inserted.
As a result, designers must manually remove and reinsert the UDF in each affected part.

This process:

  • Is time-consuming.

  • Breaks references in assemblies or downstream applications (e.g. CAM, metrology).

  • Causes inconsistency in feature definitions across models.


3. Are you using a workaround? If yes, please describe it.

Yes, the only workaround is to manually delete and reinsert the UDF in every affected model.
This approach:

  • Requires manual redefinition of all references.

  • Often leads to broken links in assemblies and drawings.

  • Is error-prone and inefficient, especially when many parts use the same UDF.


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.

We use UDFs in a Model-Based Definition (MBD) process chain, especially for:

  • Standardized port geometries.

  • Thread features.

  • Manufacturing annotations.

These UDFs are used consistently across hundreds of parts. When one of these features is updated (e.g. tolerance change, geometry improvement), all instances should ideally update automatically.

Our idea:

  • Introduce a UDF update mechanism that detects if the UDF definition has changed.

  • Give users the option to update UDFs in referencing models, preserving references where possible.

  • Optionally, a notification or update prompt could be shown when opening the model.


5. What impact does this problem currently have on your organization?

  • Affects 20+ users in Design, CAM, QA, and Metrology.

  • Leads to significant manual effort, especially for parts used in product families or variants.

  • Causes data inconsistency when UDFs are not correctly updated across all parts.

  • Risk of manufacturing or inspection errors due to outdated feature definitions.

This limitation affects the overall efficiency of our digital process chain and slows down industrialization efforts.

4 replies

Community Manager
Jul 21, 2025 6:58 AM UTC
Status changed to: Clarification Needed

Thank you @LuccaF for publishing your idea. However, we require that you organize the information of your idea as per the questions listed in the submission form, also listed below. Please make sure to include screenshots/videos to paint a clearer picture, if necessary. 

Please let us know within the next two weeks.

1. What version of the software are you running?.
2. What is the problem?
3. Are you using a workaround? If yes, please describe it.
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.
5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)

Additionally, I invite you to check out this topic where PTC executives explain product managers' approach to customer ideas and input for product roadmaps.

Please see examples of well-documented ideas:

Option to Import STEP file as Inseparable Assembly... - PTC Community 

 [Eztol] Rename action not synchronous in Eztol - PTC Community 

 Always enable ability to 'Add View Label' in a dra... - PTC Community 

Feature parameters can be input and changed togeth... - PTC Community 

Community Manager
Jul 21, 2025 12:08 PM UTC
Status changed to: Acknowledged

Thank you @LuccaF 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.

Jul 21, 2025 7:39 PM UTC

Hello @LuccaF ,

 

What kind of UDFs are your company using?

Were they created as "Stand Alone" UDFs or as "Subordinate" UDFs?

The behaviour is different between the two.

 

A "Stand Alone" UDF does not preserve any associativity between the UDF in the original part and the applied part. I think you are using UDFs created with this method. The only way to update an UDF that was already applied to a part, is to do a Replace UDF and re-specify an instance if it was created with a family table to make it update in the final part. 

 

The "Subordinate" UDF variant, is supposed to maintain the associativity between the original and the instances, ie, in all the parts that use that UDF definition. So, if you update the definition of the UDF, all parts that are opened and regenerated will inherit the updated UDF. Which is the desired behaviour in most cases, but which also has its drawbacks, since it will update even parts that have already been produced and should not be modified. This means that parts that belong to standard libraries should not be modified, and not use this kind of subordinate UDFs, unless the user opts to create new standard parts if the UDF changes. This might be difficult to manage manually. Probably this is easily managed by Windchill, I don't know. 

LuccaFAuthor
Jul 22, 2025 5:58 AM UTC

Thank you for the explanation @S_Edgenear !
In our case, we are using subordinate UDFs only, because we want to preserve associativity and enable updates across multiple models.

However, we’re running into a specific issue:
Whenever we modify a feature (KE) inside the UDF definition, all placed UDF instances in the referencing models lose their link to the original UDF. Creo shows a warning message during the UDF edit, indicating that changes break the connection.