Link assets from local documents
The cloud support for shared Xd libraries/components/fonts/colours etc is exactly what I've been wanting - except I can't use it because I don't use the cloud to save my files (I have to use our internal server).
The same features but importing from files outside of the cloud is really needed!
João Nascimento commented
Upcoming migration of our entire design dept. workflow to Figma due to company policies alone. Unfortunately we'll have to ditch XD to comply with security policies. + I don't want to be depending on Adobe servers (nor anyone else's) to store our work.
Jim Doria commented
Our locked-down IT structure precludes use of Adobe Cloud for anything. I need to be able to keep libraries locally!
Silver Jade commented
I'm so annoyed you mob took away component sharing between local files. What the hell were you thinking? There's too many people out there that are required to work locally due to company policies. Mine included.
Frankie Loscavio commented
100% Agree - Linking assets via Adobe's cloud does not work for Enterprise clients due to internal security measures.
Need the ability to link documents locally, a library file or from a internal server.
Adobe XD, listen to your users on this. You forcing the "cloud" on all users is a losing strategy. Many enterprise users can't afford to send all files and versioning to you and your "secure" systems. We use GIT and need full control over versioning and document ownership.
This is a big pain point for me.
Here's my scenario.
#1: I don't want your cloud
I work with more than XD files (shocking, I know) and each of my projects is collected in a Git repo. I have no interest in throwing my files into Adobe's cloud, especially since it doesn't work with my other file types (code, Sketch, etc).
#2: One doc doesn't have enough space for a serious app
So I end up with multiple files to make room for all the features of the app. If XD had pages, like everybody else, I'd just build one mega file … but it doesn't. I usually end up with separate documents for each major feature area. For an app with pages, I often run up to 10 to 20 pages depending on the complexity of the app. With the pain and suffering of XD, I try to keep it to 5 documents or less.
#3: I'm not always connected
Sometimes I'll work from a trailer in the mountains. That's a pretty cool part of my job. But Adobe doesn't seem to think I should do that. In their eyes I'm connected or I'm not working. Okay then.
All that to say …
Linking to local documents as shared libraries is table stakes for this feature. Kano says, "Basic!"
Art Sunward commented
Hello Adobe Team,
Strate to see there is no local sync/link option but only could base one? Any solid reason for that restriction?
Why not keep them both? The program is good and could be the next standard for UX/UI development.
The problem is really the lack of few important options, one of them, the most important is syncing with your local machine/ server before you decide to go online. Such restriction making the product of building "Powerful Design Systems" to look cheap, and fake.
Please fix that if you want your business to run smoothly in the future, and to satisfy our creative design experience).
+1... I am not always connected while working, and working often in trains and such...
I don't think Adobe will EVER implement this functionality.
@Shawn Kelshaw is absolutely right. it's a lock in strategy
[Deleted User] commented
This is madness, how can you not have an option to link assets from local files...
Shawn Kelshaw commented
Adobe has run out of revenue stream ideas and is forcing users to consume cloud space. Depending upon your plan, you could have up to 100GB of cloud storage. They are attempting to drive sharing and collaboration and the only way to deliver on that functionality is to sacrifice the convenience of linking local libraries and assets; otherwise, they will have a different set of customer complaints... like: "why can so-and-so comment on my designs?" Answer: "because your files aren't in the cloud." It's a win/win for them. They drive activity (through sharing and collaboration), they increase revenue (cause eventually you're likely to need more space) and they remove an entire set of complaints and support challenges of designers that would otherwise work locally and still want to "share and collaborate" from time-to-time... "as a user, I want to work with local files..." Can you sayyyy... backlog?
It's hard to believe that XD is still missing this very basic functionality. How much longer is it gonna take to add this Adobe?
For me it is also necessary to link local files (enterprise environment, not allowed to use external clouds). And I see no reason (except of questionable strategical resons) why Adobe withholds this feature form users. It is not even a feature because linking to cloud documents is most likely more complex than to local ones. For me the whole file handlig looks like a typical "dark pattern" and one of the user story for developing XD was certainly "As owner of Adobe Cloud I don't want the user to be able to use local documents." - Sorry for the sarcasm but this is really frustrating me.
We like keeping the documents local. For an innumerable amount of reasons. The fact that companies push for online workflows is just to lock us into their products, and at some point, probably get away with claiming the documents don't even belong to us. So yeah, this should work offline like it does on Sketch. It's one of the main reasons we haven't fully switched to XD from Sketch.
Kim Busch commented
Agree - Linking assets via Adobe's cloud does not work for Enterprise clients due to internal security measures.
Need the ability to link documents locally or from a internal server.
Support for only linking assets via Adobe's cloud doesn't work for many enterprise client given the uncertainty of security.
Copy and pasting text with character style applied into a new document should retain that style and ideally sync it back to the master.
Without requiring the document to be in the cloud.
As mentioned by other customers the cloud, magical as it is, doesn't always work for a variety of reasons, often to do with enterprise and security. Thanks :)
Nicholas Crofoot commented
Would give a hundred votes for this if I could. Same issue as the others. Our company is super security conscious and requires everything to be on internal systems.
Agree. The ability to link local files as libraries with components, colors and text styles is very important. Sometimes there's no/bad internet connection, using internal server, etc. I've also had problems with linked cloud files and this blocked me from working. I cannot rely entirely on XD at this moment.
Oh right, I forgot that you could only link assets from a cloud document. Yes, I would suggest merging in to the feature request you've mentioned. It would be helpful to be able to link to documents that might be hosted in google drive or elsewhere as well rather than just as XD cloud document.s
In cases where I've shared an XD file that has components linked to a cloud document, those components are all broken links to other users unless I share the cloud document too. Users can 'Relink' to the cloud document, but there is no way to 'Relink' to a local XD file. There are cases where this might be useful