Component pattern suppression changes from full to partial suppression when switching between model states

[manish.sharma9LBKQ]

Hello,

When I'm working with model states and suppress a component pattern in one model state and switch to another model state where the said component pattern is unsuppressed and switch back to the previous model state where it was fully suppressed, the suppression automatically changes to a partial suppression.  Meaning, it changes from a pattern suppression to an Instance suppression.  Please see attached screenshots.

What could be the issue here, and how do I resolve it?  This is not the first time I have seen this.

I am using Inventor 2023, and I have all the latest updates installed.

Thank you,

Manish

[mluterman]

If I'm controlling my .iam using Model States, then I use "Suppress/Unsuppress" (with ViewReps set to "Primary").

If I'm controlling my .iam using ViewReps, then I use "Visible/Invisible" (with Model States set to "Primary"/all Unsuppressed).

It looks like you're combining both; not impossible, but that's where it can get confusing.

[johnsonshiue]

Hi! I guess between the two model states, there is a change in the number of instance, right?

Many thanks!

[manish.sharma9LBKQ]

Yes, for a couple of component patterns there is a change in the number of instances that I control with the parameters.  But there is also an inclusion/exclusion (Suppress/Unsuppress) of a component pattern between the two model states.  However, when I switch back and forth between the model states, the fully suppressed component pattern rather changes to a, for a lack of better words, partial suppression.  I believe that is not the same as a change in the number of instances.

I hope that makes sense.  Thanks!

[manish.sharma9LBKQ]

I'm confused here.  I'm not trying to control the visibility of the pattern, but rather the suppression between the model states, so I can exclude items in a particular (entire) pattern from the BOM in one model state, but want to include those same items in said pattern in the BOM in another model state.

And setting the ViewReps to Primary and Suppressing/Unsuppressing did not help.

Thanks!

[johnsonshiue]

Hi Manish,

There could be a bug in this workflow. If possible, please share the files in zip here. I would like to understand the Model States suppression behavior here.

Many thanks!

[mark_bohman]

Good morning!

To elaborate on my colleague Manish's issue:

We are currently using Inventor Professional 2024.3.3
We use our 3D models to drive the Bill of Materials (BOM) in our ERP system by use of Model State assemblies.

What we are seeing is that when a component pattern needs to be suppressed for one Model State (which is a Part Number in our ERP system), only the first member in the component pattern is suppressed.
This occurs with the following workflow:

1. [Primary] Model State is made active.

2. Manage tab >> Edit Member Scope

3. Suppress Component Pattern ("LOUVERS" for this example)
>> Everything looks fine at this point, and the BOM returns a QTY of 0 for EN0148-06, which is correct.

4. Change to another Model State ("EN0187-000-MG" for this example)

5. Change back to [Primary] Model State
>> All of the louvers except for the first one in each pattern become visible, and the BOM returns a QTY of 16 for EN0148-06, which is incorrect.

Please give this a try with the attached model EN0187_FEA.zip (model filename is EN0187_FEA.iam).

Many Thanks!

Mark Bohman

[johnsonshiue]

Hi! Many thanks for sharing the files and the steps! I am able to reproduce the behavior. This has something to do with suppressing a component pattern and also having table-replaced the pattern source component. This could be a limitation. I will work with the project team to understand the issue better.

Thanks again!

[mark_bohman]

Johnson,

Thank you for the quick response!

It is odd that this is an issue because it works just fine in an iAssembly.  However, Model States are far more useful, especially since all of the child members are included in one file, which reduces work in Vault because only one file needs to be managed versus a parent and several child member files.

After installing Inventor 2024, we have transitioned our workflow to use Model State assemblies instead of iAssemblies.  However, we have close to a decade's worth of iAssemblies that we use in our Model State assemblies because those designs are good and Released in Vault.
What we are seeing is that this issue occurs when using iAssembly child members in a pattern versus Model State components in a pattern.
The Model State-based component patterns work fine in both the Model State and iAssembly environments.

However, the iAssembly-based component patterns only work in the iAssembly environment.

What we need is for Model State assemblies to work with iAssembly-based component patterns just like iAssemblies work with iAssembly-based component patterns.

Thanks Again,

Mark Bohman

[johnsonshiue]

Hi Mark,

Many thanks for sharing the files! I am working with the project team to understand this behavior better. It does seem to be related to Table-Replace. Yes, as you have found out it works fine in iAssembly.

Just share a bit background on this issue, though iAssembly and Model States work fairly similarly, iAssembly Exclude and Model States Suppress are quite different. iAssembly Exclude is achieved by hiding the components and also deduct (exclude) them from the BOM table. But Model States Suppress means the particular components are unloaded from the memory and the BOM quantity is adjusted accordingly. It should have work regardless.

Thanks again!

[damian.lewczyk · Accepted solution]

FYI
Report ID: INVGEN-83159
Fixed in: 2026.1, 2025.3, 2024.4.