Fusion library BIG fail

[nnovotney]

Fusion 2704.1.36 x86_64  Active Plan: Subscription  Windows 11 Pro 25H2 (26200.8973)

I didn't like the testpoint I had in the schematic, so I right-clicked schematic and brought in the component into my project lib to edit it to my liking.

I wasn't expecting it to arrive in my lib with 30 different variation flavors---I only wanted the exact one in the schematic.... there should be an option to bring in the SPECIFIC instance, not all the variations baggage.  Anyhow, proceeding along...

To avoid some ambiguity, I right clicked and renamed the overall component (as testpoints-mine). 

I picked one of the variations and right_clicked it & renamed it (ATP_20mil).   I edited its foot print to my liking & saved all.   Note I used ATP rather than TP , so it would stand out better during this problem, or be more alphabetically sorted

However, going back to the schematic, the component (testpoints-mine) shows up , but the renamed variation (ATP_20MIL) is nowhere to be seen.  I also closed down fusion  & tried again minutes later, no luck. Also tried update design from all libs as well.

typing in one of the other variants , shows up   WORKS

typing in my renamed variant (ATP_20MIL) shows nothing (and as mentioned does not appear in the dropdown list)  FAILS

As another test, I right clicked a different variation TP127R and renamed it  FUSIONBARF & saved without making any edits at all.   It is also nowhere to be found in the schematic placer

WHY???????????  WHY???????????

[Taylor.Chris]

It looks like this could be because you are renaming the footprint, not the variant.  Try using the panel on the right side of the component editor, that's where you see the variant names.

I'm still surprised it doesn't show up for the search - but I think what you are wanting to do here is rename the variant, not the footprint, which needs to be done on the panel on the right (variant panel) - right click one of the variants and hit rename.  Give that a try and let me know if it is behaving as expected.

This aspect of the content manager has been a point of confusion for people before, we are exploring better solutions.