We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
Hello, I was wondering if anyone can help.
I created multiple XD files all linked to the same cloud library in regards of common components, colours and character styles.
This is great, however now I need to do the same job for a different brand. Is there anyway I could duplicate my XD files (which don't need any other changes other than common styling) and link it to a different library that will have the same compontent names?
I used to be able to do it with physical files, deleting the main one and replacing it, but now it seems impossible with cloud library and if you duplicate a library it just messes up with my original file (which I had to relink one by one thinking the old method could have worked, but completely messed up my files).
Why don't you save your Cloud-File (the one with the components) to your Harddrive and then import these assets in your copied files?
Or – move all the components/assets from the open Cloud-File to a CC library – and then connect it to your new files.
Thanks for reaching out and sorry for the delay in response. If I heard you right, it looks like you want to essentially copy your source file and library to create a second version, with everything still linked. Then I am afraid to say that is not possible.
For now, you can make a copy of the source document (via save as) and create a new file, and then publish a new library from that new source file. That will essentially copy your design system.
Let us know if that helps.
I essentially did the same what you outlined here.
Old UI Toolkit in XD Libraries
Opened Old UI Toolkit XD document
Save As (for new UI Toolkit)
Published new library
Revised Components, Colors, etc.
Now when we try to utilize both old & new UI toolkits in one XD project file, XD is confusing the components, it seems to favor the component library that was placed first in the XD project file. We think there's something going on underneath the surface that we cannot see, as we do not have this problem when we recreate the component fresh. However that defeats the purpose of being able to efficiently update our screens via CC libraries. Can you look into this bug?