Component override lost when copying between files
Our preferred workflow is to have a Xd-beta file for new development. When changes here are implemented the design gets moved to another file.
However, when copying artbords that contains components with overrides, these overrides are lost when the artbord is pasted in a new file. (both Xd-files are connected to the same master component file)
Would love if this could be fixed.
Hi All -
Can you please detail out what’s your current workflow today in XD that lands you into that situation?
In other words, are the documents that you’re pasting into linked to the source document? are they “Saved As” versions of the source documents.
This extra info will help us identify what the issue is.
Sherif- I have a master file with all my components that has overrides. When I open a new document (since XD doesn't support pages yet), and paste an component into that new file.. all the overrides or recent updates to that source component in the master file as not translated to the new document. This is extremely frustrating.. as any time I try to build new docs I have to start over with the components.
Danae Botha commented
JFC, when are you going to fix this? I need to keep whatever I did to a component no matter where I copy it to. I'll tell it to reset if I want it to. This - along with your frankly absurdly terrible co-editing functionality - is one of the reasons I'll probably migrate my whole team to figma soon.
Your logic is bad and you should feel bad.
Mike M commented
Ok, here are my issues with master and instance components, which I believe others are having this issue with, is the flexibility of them.
-- Use Case --
I've created a master component for a resource card with hover and active states, and I want to have multiple cards that may have different types, colors, names, etc. I use the base master and create instances of the component to make these different type cards, all based off the master component.
My co-designer then wants to move these modified instance resource cards to another XD file for a second version of the designs using the new resource card designs that were approved by the client, keeping the same changes and states that were modified.
-- Current issues I've encoutered --
If I copy modified components into another version of an XD design document, they revert to the master component and I or my team member has to re-do them. We cannot resolve it other than manually redoing the work we just did.
--Solution to issues I've thought of --
A. The instance should retain the modifications and not revert to the master component.
B. Give the user a notification/option to convert the modified component as a new master component in the new document.
C. Give the ability to create new master components from modified instance components, keeping all states and modifications as a new master component in the current document, and then can be brought over without issue.
Thanks in advance for your time and consideration in this update/feature to XD.
I experienced the issue when trying to copy the same component from one file to another that were Saved as versions of an original document. There were no linked components because the main source wasn't my document to maintain. Copying and pasting would revert any overrides to the original state of that component in that file.
However using a different set of files that do use components from a linked master document that I made and maintain myself, this doesn't seem to be an issue.
Hope that helps.
yannick frisart commented
This is indeed a very annoying problem we also ran into, however after talking to customer support it seems to be related to the version of the component being out of sync between the source file that it's copied from to the destination file.
In that case XD opts to reset the component to their default state, rather then informing the user about that. (Not to cross reference issues, but after understanding that this causes that. I created the following issue as a possible solution/clear description of what causes the issue at hand. https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/42147112-add-model-that-warns-user-if-component-that-they-a)
Sean C commented
I have to agree. There are a lot of really small annoying things like this that really add up within XD.
Chris Cappella commented
This seems more like a bug, than a feature request.
This is super annoying. Some sort of solution would be really appreciated.
Cynthia Peterson commented
I've seen several mentions of this on the Adobe Support Community, but none have been adequately answered or resolved. Is this how the current functionality is "supposed" to work? If so, are there any work-arounds?
Update: Here's one possible way around this, that just worked for me. Before pasting component instances with overrides into a different file, first delete the corresponding component masters from the destination file. (However, this is only useful if you don't have existing instances in the destination file that need to remain linked.)
Joo Chung commented
This is one of the most ridiculous lack of functionalities I have seen. Why, why, does it ever make sense to undo the user's work when copying and pasting elements? In what world does this make sense?! If I copy an edited instance from one file to another, it MUST retain all of the edits in the pasted version. If people want to copy the default version, you could also include a way to paste the default version. It's amazingly boneheaded that UX software would just brazenly obliterate the user's explicitly created work. Ugh.
Adam Trabold commented
Yes, this is so annoying! Often am stealing pages from other documents / flows, and have to re-set all component states / copy / etc...huuuuge time suck.
I often create similar styled apps layouts. When I copy buttons with overrides from another document and I paste them into the new document. XD includes the component but it disregards the overrides, so the buttons are pasted in their default state with default text. This is alarming, because now It requires you re-do all the overrides in the new document, which is a lot of duplicate work now.