Updated Inventor, now cannot work with Assembly

[cc01720]

Hello,

I have been working on an assembly between two devices using a USB and recently updated both devices to the latest version of Inventor, thinking that if both versions were updated to the same version, that there would be no issues with working between them.

Unfortunately I now cannot select individual parts of the assembly on one device, but it is fine on the other. The attached image shows on the left shows the Model tab where I can select each part individually and manipulate them as I wish, and the right shows the Model tab of the other device where I cannot. If I hover over the assembly itself on the latter, or select individual parts, the entire assembly goes blue as if entirely selected.

Is there a way to prevent this from happening?

Thank you!

[ampster40]

first guess with the limited info is maybe the assy on the right has not been saved yet?  ie, note the missing assembly file extension next to the name of the assy while ".iam" is next to the assy on the left.

We could use more details such as what version of Inventor you are using as well as the files if you are able to share them.

[sundars]

@cc01720 

It looks like you have two different versions of Inventor. The left browser shows the files in a later version, while the one on the right shows the same assembly imported node. Some files may have been saved in a later version resulting in this kind of problem.

Use the Open File Dialog in inventor and click on one of those files and you can check the version (it should be displayed as a string below the file name).

Thanks

-shiva

[CCarreiras]

Hi!

The image on the right is an import operation, (not an open operation) and this happened because you are trying to open a model created/saved in an upper version of Inventor.

If the software is in the same version on both pc's,  check the updates.
Since now the updates bring also new features, both versions must be at the same update also.

Must recent version/update: 2023.2.1

[johnsonshiue]

Hi! This was a defect in 2023 RTM build. Please install 2023.2 update followed by 2023.2.1 update.

Many thanks!

[cc01720]

Thank you all for your advice

@sundars both dialogs display "Last Saved: Autodesk Inventor 2023 (27.0.15800.0000)".
@ampster40 I moved the files across from USB and then copied to the local drive. When I use Save As on the assembly (just named it Assembly1 in error2.png), the .iam extension comes up like on the other device where the assembly works as normal. Still has the problem, though.

@johnsonshiue @CCarreiras I had both devices updated to the latest version in the first place. There were a few updates to do each (the same ones), but I believe I didn't update them in the same order. Would this be an issue? I assumed if all updates were made, that it wouldn't mind the order in which I completed them. 

Looking at the problem-causing device now, I have just seen that there might be a problem in Autodesk Desktop App: after restarting the device and reopening the Desktop App I get a option to update Inventor to "Inventor Professional 2022.4 Update". When I press "Update", it downloads and then tells me that the update is already installed, and then the option disappears. This cycle repeats for each restart.

[CCarreiras]

Hi!

Check here in both pc if the build is the same:

app issue you described is a bug, it will updates eventually.

[cc01720]

Interesting they are different, but everything is updated in the Desktop App. Would a reinstall fix this?

[sundars · Accepted solution]

Hi @cc01720 

On the machine which has 2022 simply install 2023. Then both machines should have the same latest Inventor version. Typically, a version of Inventor never stomps or installs over another version.

You can navigate to C:\Program Files\Autodesk\ and look at all the versions installed there OR you can look at Control Panel + Programs and see whats been installed.

Glad the problem is understood!

-shiva

[cc01720]

Issue resolved thank you all.

Turns out I installed the latest version 2023.x.x when I thought I did, but I didn't change the Windows default application to it (it remained defaulted to the 2022.x.x version), so after simply changing the default to 2023.x.x, it worked.

I uninstalled 2022.x.x for good measure.

[sundars]

Nice! Glad its resolved. Thanks for the update.

[CCarreiras]

Well, you've got the answer on the images you posted... one is 22 and the other 23....