[SERIOUS PROBLEM] Import component could overwrite footprint with the same name

[anranlioculus]

I was trying to import a component from a local library file.

Initially, I thought I couldn't import components because they have the same footprint name.

So I posted this:

There is only one option to overwrite the existing footprint with the footprint from the imported component. This doesn't make any sense, and in my opinion, it's very improper behavior. There should be options to rename or use the existing footprint.

Since there's no option to import symbols and footprints from the local file, my current workaround is to import into a temp library first.

However, later I found out that I couldn't repeat this behavior. Every import I did later, whether from a local file or from another hub library, overwrote the existing footprint with the same name without any notification. 

This only happens to footprints, not symbols. The symbols will rename automatically.

I'm not sure if I did anything wrong. I feel like this is a very serious problem since a wrong footprint could replace the genuine one silently.

[jorge_garcia]

Hi @anranlioculus ,

Thank you for reporting this. The fact that it was not reproducible is really concerning. If you do find a way to reproduce this please let me know and feel free to reach out.

Best Regards,

[anranlioculus]

No, this is reproducible. See the screenshots for before and after the import.

What's not reproducible is the map pads of footprint pop-up window, which should have prevented the silent footprint overwrite.

The component name and description, variant name, footprint and description were all modified and saved before the import. 

Only the footprint name was left unmodified before the import.

[jorge_garcia]

Hello @anranlioculus ,

I hope you're doing well. I now understand, yes this is definitely serious I have shared it with our libraries team.

Let me know if there's anything else I can do for you.

Best Regards,

[Closed-Loop-Bot]

Thanks for bringing this to our attention. We're investigating the issue, and you can reference ticket FUS-274388 when communicating with Autodesk to find out more. Once the status of this will change, there will be a follow-up forum post made.