Model states not working for patterned parts in Inventor 2022 Read only version

[gcross]

I'm reviewing IV 2022 RO for use by management for review of models & assemblies & noticed that the Model states are not functioning on parts used in a pattern.

I wanted to list "Full Model States functionality" as a Pro but I guess it's a Con.

Is this a bug or as designed?

Anyone know of any other non-obvious limitations?

[johnsonshiue]

Hi! I guess this may have something to do with the need to "write" to the Model State (file within file; local storage). Try this test and see how it works.

1) Create a drawing view of the particular Model State in the assembly.

2) Save files.

3) Open it in RO.

Are you able to activate the Model State?

If possible, please share an example so we can take a further look.

Many thanks!

[gcross · Accepted solution]

Hi Johnson,

False alarm...I checked & it turns out I had inadvertently overwritten all the edits on the part that was in the pattern so it appeared they did not respond when various top level Model States were selected. I'm in learning mode for Model States.

I think I was attempting to make an edit in a part for one model state apply to all & made all feature edits match the Master unintentionally.

I fixed it & the patterned parts are now correctly responding to each top level model state I created IV 2022 RO.

I'm really appreciating Model States, that feature alone made IV2022 worth it.

[gcross]

Hi Johnson,

I'm experiencing another issue with Model States that I need help on.

Getting the attached error message regarding the Model States Excel file.

It states "Detected potentially damaging errors in the table

                 Unable to interpret a column header.....<invariantLable>....

                 Multiple columns have the same name:..."

First thing I did: The "filename" in excel file did not match the header name so I edited the header to match the file name & saved. I still get the error message when I click on a non-master Model State or open the Excel file.

Can you help? 

[johnsonshiue]

Hi! The error indicates that there are duplicate column headers. It means that two or more columns have the same header. Inventor does not know which one to use. Please edit the Model States table and set column width so that you can see the headers clearly. There might be duplicates.

Many thanks!

[gcross]

Johnson,

I attempted to delete one of the columns with "invariant" as part of the header. The matching column did not have the "invariant" in it so I assumed that was the one to keep.

I deleted the potential offending column saved & closed the Excel file. Then I saved the IAM file & reopened it.

The error persists & the excel file appears the same as if I did not edit it.

Any ideas?

[gcross]

Also, the both the column header's file names do not match the actual IAM file name. I had revised the actual IAM file name shorter earlier. But the Excel file shows the old previous file name. I even revised all the iProperties to match the new file name but it did not help.

[johnsonshiue]

Hi! I think I know what has happened. Most of the editing workflows at the same level are captured by Model State table. But, I don't think renaming is one of them (except parameters maybe). It is because there are just multiple ways to rename an object in Inventor. You will need to adjust the table accordingly.

Many thanks!

[gcross]

Johnson,

I have tried repeatedly to edit the table to delete the problem column but I cannot get the edit changes to persist despite saving the Excel table file & closing it.

I also completely deleting the nested IAM that is the problem file referenced in the two table columns.

The table will not change even though I deleted the iam referenced in the table columns . I can open & edit the table but it just stays the same as before after save/close/reopen.

The same error message still comes up even though I deleted the offending IAM file.

How can I fix this?

[johnsonshiue]

Hi! I will need to see the files. If possible, please share them with me in zip directly [email protected].

Many thanks!