Skip to main content
Aug 27, 2025 7:09 PM UTC
Acknowledged

ModelCHECK Assembly should compile all the user messages before running.

Related products:Creo Parametric

1. Describe the Problem

When the user runs ModelCHECK on an assembly.   ModelCHECK looks at each model individually.   If the user has objects in Read-only they have to wait and click "OK" for each object.  This wastes a lot of time.   ModelCHECK should first run all the models against the conditions.mcc file, then report all the model warnings at one time.   

(view in My Videos)


2. Are you using a workaround?
Be very careful to not click "All Models". Or, kill the Creo Parametric session. Or, waste time waiting and clicking.

3. What is the use case for your organization?
Any user that want to us the All Models options should be able to do so confidently.

4. What impact does this problem currently have on your organization?
Not sure, in my small assembly demonstration, we waste 20 seconds each time ModelCHECK would be ran. But this would be expanded by larger assemblies.

12 replies

Community Manager
Aug 28, 2025 12:37 PM 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.

Sep 2, 2025 8:24 PM UTC

It would also be nice if ModelCheck gave a progress bar. It's super "fun" waiting for ModelCheck to run on large assemblies with no sense of when it will complete.

N.BarnesAuthor
Sep 2, 2025 8:32 PM UTC

A progress bar could be a component of this request.   

  • ModelCHECK develops a list of all the parts requested to be checked.   
  • Adds a column with read only/checkout status for each item.
  • Adds a column with the checks to be ran on each item.   
  • User can filter the list to show only items to be checked.
  • User can clear read only or start a checkout from menu (like other Parametric operations can)
  • User can cancel or confirm that ModelCHECK should run. 
  • After the user confirms what is to be checked, then a completion status column against that list is added to the list. 
    • Errors/Warnings could be also included while the checks run, but not really necessary, since that will be available in the main report.
Sep 18, 2025 7:20 PM UTC

I reported this to PTC last year and it was reported fixed by SPR 15461473 in 9.0.10.0, 10.0.7.0, 11.0.3.0, and 12.4.0.0. I just checked it in 12.4 and it does appear to be fixed. (See CS419431). Is it an issue for you in one of those or higher versions?

N.BarnesAuthor
Sep 18, 2025 7:39 PM UTC

@JamesAvis We are currently on 10.0.8.0.    The issue you noted looks like a related problem.     But, in this case the assembly is already checked out, but the components aren't.    Maybe the fix that was implemented doesn't catch this case. 

Sep 18, 2025 8:55 PM UTC

@N.Barnes Yeah, looks like it's fixed for some use cases and not others. I'm going to revisit this through tech support, since it was a tech support case, but that should not stop this idea from being looked at. Whether it's an SPR or an Idea, this is a big usability issue!

1-Visitor
Sep 25, 2025 3:30 PM UTC

Can't the conflict window regarding the read-only state of the model be avoided with the hidden config.pro option “dm_auto_conflict_resolution yes”?

Sep 26, 2025 3:28 PM UTC

@DomenicLaritz Yes, that is the workaround. If you're planning to use Modelcheck All Levels, or even Save As Backup (if modelcheck Save mode is defined), prior to the build this was partially fixed in, or apparently with checked out items on a "fixed" build, you absolutely must enable that setting if it's not a small assembly. But you'll also need to ensure dm_checkout_on_the_fly is set properly.

N.BarnesAuthor
Sep 26, 2025 3:43 PM UTC

Thanks for the information about the hidden option work-around.    That might work for some of our user base.   In general,  I hesitate to allow ModelCheck operations to checkout or continue modifications on a bunch of parts.

1-Visitor
Sep 29, 2025 5:41 AM UTC

Shouldn't it also help if the config_init.mc settings "CHECK_ALL_MODELS N" and "SKIP_MODELS Y" are configured?
This should ignore models that haven't changed since they were opened (and this should actually apply to the read-only models).