Can I keep the Component ID?

Hi @Motele, Thank you for reaching out about this!

As we await input from our community, could you please provide more details about the Component ID to help us better understand the situation? What does the Component ID refer to?

If any members of our community have solution or workaround on this, please feel free to share them here!

Thanks for getting in touch. Hope to hear from you soon!

Hi @Junko3 , thanks for reaching out. The use case involves a header component as part of a Design System. I didn’t build the original version of the header but was assigned the task of rebuilding it due to various issues with accessibility and properties. My idea was to create a new, correct header and replace the old one once it was finished. However, I wasn’t able to replace the old header (and I think it attempted to restore the old header component). It seemed to me that the only solution was to modify the existing (old) header built by the other designer. It would have been much easier for me to build a new one (next to the old comp) and simply replace the old one.

Hope this helps.

Hi there, Thank you for the details!

While it may not align perfectly, I’d like to share some resources that might help in this situation:

• Swap components and instances
• Swap style and component libraries
• Components, styles, and shared library best practices

I believe there are designers in this community who have faced similar challenges.
If anyone from our community have any insights or workarounds for this situation, please feel free to share them!

Swapping components/instances is wonky, it took us a very loooooong time to flush out old components. Your best bet may have been to do the work in a branch, then merge it when ready.