Skip to main content
Oct 7, 2025 7:29 PM UTC
Acknowledged

Way to configure CreoView to not add Default and Empty View to files

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

1. What product and version are you running?
Running on Creo Parametric 10.0.8.0, CreoView 11.1, Windchill 13.0.2


2. What is the problem?
Representations generated from Annotated CAD models with combined states are adding a Default View and Empty View when representations are generated from Windchill.

The response was that CreoView always adds these states.

It is causing confusion when providing representations or users are looking at representations and the data has information not in the model creating a disparity with the viewable, which makes the delivered file undesirable for viewing model-based dataset.

Would like an option to make it so these aren't part of the CAD representation, or have the ability to set which Viewable State the file would open in, and if those 2 Views have to be there for CreoView have a preference/option to hide those by default.


3. Are you using a workaround? If yes, please describe it.
Telling folks that are viewing the file "Everything in the CreoView representation is generated from the model EXCEPT the Default View and Empty View, but the one called Default under Viewables is from the model"

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.

Looking to make the deliverables from Model Based Definition datasets as digestible as possible and consistent between viewers to minimize confusion and adoption.

5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)
Causes confusion for users digesting and adopting Model Based Data sets.

1 reply

Community Manager
Oct 8, 2025 2:45 PM UTC
Status changed to: Acknowledged

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