Skip to main content
Jun 2, 2025 5:23 PM UTC
Acknowledged

ModelCHECK "Required Relations" block capability

Related products:Creo Parametric

1. Describe the Problem

In Creo Parametric it can be helpful to have a common required block of relations to drive company standard attributes or calculations.    For normal relations and comments ModelCHECK will only check for the existence of a relation or comment.  There is no position check.     (For solve blocks ModelCHECK does understand order dependance).   


2. Are you using a workaround?
Manual Checking

3. What is the use case for your organization?
Checking of models prior to release for compliance to company standards.

 

I want the relations to look like

 

/*Begin Required Common Relations
CDA_CAGE_CODE=CAGE_CODE
/*Comment About Contract Number Should Be Below
CONTRACT_NUMBER=CONTRACT_IDENTIFIER
/*End Required Common Relations

 

But this will pass

 

/*Begin Required Common Relations
/*Comment About Contract Number Should Be Below
/*End Required Common Relations
CDA_CAGE_CODE=CAGE_CODE
/*Comment About Contract Number Should Be Below
CONTRACT_NUMBER=CONTRACT_IDENTIFIER

 

Using this configuration

PRT_COMMENT Begin Required Common Relations
PRT_RELATION CDA_CAGE_CODE=CAGE_CODE
PRT_COMMENT Comment About Contract Number Should Be Below
PRT_RELATION CONTRACT_NUMBER=CONTRACT_IDENTIFIER
PRT_COMMENT End Required Common Relations

 

Notes

1) I was also going to test the "RELATION_UPDATE_FILE", but I don't see a way to specify part vs assembly.

2) It would be good if the check would also report if there are additional copies of the lines in other parts of the relations.    For instance has "/*End Required Common Relations" been repeated multiple times.


4. What impact does this problem currently have on your organization?
Currently manual checking steps are needed to ensure the correctness of the relations.

7 replies

Community Manager
Jun 3, 2025 9:42 AM UTC
Status changed to: Acknowledged

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

Jun 11, 2025 12:58 PM UTC

If the relations are in your start templates, they will always be in your specific order.

I do not think there is any current mechanism in ModelCheck to enforce the formatting of lines in relations. As I have said many times in these types of ideas, if it won't drive new sales of Creo, it will not likely be implemented unless PTC does a massive rewrite of ModelCheck.

In the end, does it really matter? The information is in the file, just looks unformatted.

N.BarnesAuthor
Jun 11, 2025 10:20 PM UTC

Agreed.  They will be in new template files, but would be nice to automatically update already existing parts.   And just verify if someone has been tinkering.  

 

There have been enhancements to ModelCHECK over the last few versions.  Maybe not as dramatic as we might like to see, but there is some work happening.

Jun 12, 2025 2:20 PM UTC

Maybe something along the lines of a RelationBlock where in MC we define the block of lines in the relations that we want MC to check in a specific order.

PRT_RELATIONBLOCK_START

PRT_COMMENT Begin Required Common Relations
PRT_RELATION CDA_CAGE_CODE=CAGE_CODE
PRT_COMMENT Comment About Contract Number Should Be Below
PRT_RELATION CONTRACT_NUMBER=CONTRACT_IDENTIFIER
PRT_COMMENT End Required Common Relations

PRT_RELATIONBLOCK_END

N.BarnesAuthor
Jun 12, 2025 2:38 PM UTC

Yes, something along those lines could work nicely.    Would prefer that its all captured in the start.mcs file, and doesn't require a separate file the way that  "RELATION_UPDATE_FILE" does.

Aug 27, 2025 6:15 PM UTC
Status changed to: Acknowledged

I wanted to acknowledge this again as the PM and to say we are tracking this idea and others in our Working Group meetings. 

Nov 24, 2025 6:42 AM UTC

We always write our company relations (calculate weight/volume etc.) to the post-regeneration section.

These relations also exist as a text file, and I have a mapkey to delete all post-regeneration relations and reload the text file. This allows me to update post regeneration relations in existing parts/assemblies. I also have a parameter in the model where I store the creation date of the company relations. I check this date using ModelCheck, and if it's older than my current creation date, a parameter appears in ModelCheck containing the message "Please update post regeneration relations with mapkey xyz". This is our workaround. It would be great if ModelCheck could not only check and update the initial relations but also the post-regeneration relations.