+1

100% agree

I wholeheartedly, 100% agree. I was just updating an old mockup I did last year, attempting to simplify the mockup for presentation purposes. Everything works fine in the Preview. But as soon as I share a new link, most of my hot spots are missing. Nothing I do can fix this.

I tried saving the file as a new document. The corruption follows goes with it. I tried copying the artwork into a new document, and of course lost all prototype wiring. Now all of the components reside in the previous artwork file. I am now forced to work in a file that links to another, just so I can create a presentation.

Does anyone know if there’s a way to force XD to reset its memory of all prototype wiring?

This needs to be done asap!

This is definitely paramount!
Thanks to all the cool updates, we now have components status and much more, therefore it is almost mandatory to update our design system and rethink it in a smarter way

Please do this, it's such a hassle as now I have to recreate that master component into another file.

100% agree.

Managing components is currently a huge pain point.

That will help a lot our design flow

I need it

+1

I've got a file with design layout + design system components in the same file. Now that the project has grown I would like to relocate the design system components (not all components) to a separate file.

up up up

I think it would be great to have a workflow based on a "style master" XD doc.

Like all buttons, fonts, colors, etc on 1 XD doc,
and the other XD design files based on those linked components.

So it would be easier to communicate with devs using the nomenclature on the "style master", and be consistent on all the process.

Like: use "title1" with "color2"
or "ButtonLarge" with this blabla text
etc

I agree as well. This is interesting and definitely has potential to be a great feature.

Agreeded - When working with several people across multiple files for different sections of a project, components get created in many locations as you go.

Having a master file or design system file that final master compenents can be sent to and be designated as the new Master compenent. The other team members could then link to the master file that would update matching components and deactivate the master satus. This would be VERY helpful and increase efficiency when developing a design system as it evolves with the project.

THIS for all the reasons mentioned but also to be able to recover from breaking bugs. I reported a big that I can not predictably recreate. It involved heavily nested master components and changing the nested components and other layers in some instances. The bug would brick a file and make 'copy' and 'paste' not work for the offending components as well as 'undo' not working across the entire file. Because my master components are heavily nested, I can simply start a new file with instances and then unlink and re-componentize the top parent component as all the nested components also become unlinked.

Being able to 'make master' would be ideal. The UI could work like a 'find and replace' and suggest how many instances are in the document, how many are in other documents, etc. and at least offer me the opportunity to retarget the ones in the same document to the new master, if not all instances across many documents.

100% agree! Please make it possible to move master components from one document to another. The current way of handling a single source master component is painfully limiting!

Also for cases when you decide to create a component from a design file, and want to 'inject' it to the master design system file for the benefit of all. It would be nice to just move it as master to the masters file.