Fusion 360 Browser Has Wrong Component Names

[amagrude]

I have a Fusion 360 file which consists of ~20 inserted components with rigid joins. The Browser list of components does not consistently have the correct name. Here are two different failure cases I’m dealing with at the moment:

1. In the Assembly file, the browser lists the component name as “Fire & Spatial v15:1” even though the actual component is on v16. As the component design is updated, the Assembly file version reference remains one less than the actual current version. Additionally, this impacts only one of the two configurations in the referenced component design. The second configuration is correctly displayed, name and version reference, in the Assembly file.
2. In the Assembly file, the browser lists the incorrect component name, but not version. I have a component which is inserted into the Assembly file which displays correctly. I copied the comment design, renamed it and the configuration and made substantial changes to it before inserting it into the Assembly file. The browser shows the previous design’s name, but the updated version number. If I change the name of the configuration in the copied component, the name in the Assembly file updates to the correct value - but only while the Assembly file remains open. If I close & open the Assembly file again, the browser name reverts to the incorrect name, but correct version number, behavior.

One other, potentially related issue. If I change the name of a configuration, it updates in the Assembly file immediately. That’s how I expected it to be. However, it does not require the component design to be saved, so there’s no incremented version number. That is not how I expected that to work.

I’ve tried clearing my cache data. I'm running latest: macOS 15.6.1 (24G90) on Mac15,6.

Is there anything else I can do to resolve these naming issues?

Thank you!

[CGBenner]

@amagrude 

Hello, are you able to share the file here that is showing this behavior?

[amagrude]

Sadly, both of the Assembly files which are showing this behavior are proprietary designs. 

If I get some time, I’ll see if I can coerce an Assembly files with public domain components to fail in the same way. 

Would a diagnostic log of some kind help? If so, which?

Btw, I also tried the Service Utility Repair Autodesk and that didn’t fix either issue. 

[HughesTooling]

I think from what you've said you've made copies of designs and inserted the original and the copy into an assembly?

If you used Save As to make the copy I think you'll run into problems because the internal references in both files will be the same. This used to be a problem, not sure if it still is.

What you should do is use Save Copy As from the right click menu when you right click the top folder in the browser and this will create a unique copy.

[Victoria.Studley]

@amagrude Since you're working with Configurations, there are a couple of things you may want to check regarding the version numbers and naming.

Version Numbers

• The Configured Design (CD) and its individual Configurations have separate versioning logic, so the numbers won't always match.
• When you save changes to a Configured Design (CD), the CD itself always gets a new version increment.
• However, only the Configurations that were edited during that session get a new version increment. So, if you didn't edit a particular configuration during that session, its version number remains intact. This is how some configurations have a lower version number than the CD and/or other configurations in the same set.
• This logic prevents unnecessary updates to configurations that haven't actually changed.
• You can find more info about this here.
• You can verify and compare the version numbers in the Fusion web view.

 

Naming

• There's a user preference that lets you control the display of Configured Component names in the browser, which you may want to check.
  • Click your Profile Picture > Preferences > General > Design > Configurations.
  • Select the combination of CD Name, Configuration Name, and Part Number that you prefer.

• From what you described, it sounds like you could be experience a rename issue with configurations.
  • When you reopen the source Configured Design, does the renamed Configuration also revert in the table? Or does the new name show up correctly there?
  • If they still look correct in the Configuration Table but not in the browser of a design where they're referenced, there might be a problem to look into.

[gautham_kattethota]

@amagrude 

Changing configuration name is not a file dirtying operation, or in other words, changing the names of one or more configurations will not edit the Configured Design and hence will not require a save.  It is the same principle that is used for design file name changes.  And each configuration is its own design file.  You can rename a design in the data panel without opening it.  All designs that reference this design will automatically reflect this name change without requiring a save.  This is how Fusion works and configurations is following the same principle.

You mention that it is not how you expected it to work?  Is there a reason why you want a name change to be a file versioning operation?

Gautham