Option to keep share links after filename is changed/ save as in XD
Apparently some people want to automatically delete the already created links each time they save their file as a new one.
But this is not the case for everyone!
I need to keep my link history even if I saves as a new file.
(I don't get how people can not just create new links)
This was a very important good point of XD for my team, clients and I, and now I have to explain to everyone that I will have to share a new link, or simply keep the same file even if I have big change on it.
I'm sooo not happy about your decision.
Give us the choice please!!
Talana Tisdale commented
Adding in my vote for this functionality too! This is not at all ideal for how most design teams run within an organization - we send a link out for review/testing of the prototype to various stakeholder groups, and then if one small thing needs to be changed or is caught post-sending, we have to send out link after link after link every time we make an update!
It should work like InVision or Figma - one share link works per project no matter what you update.
Extremely frustrating, thinking of switching to Figma for this reason alone.
This is "Adobe Experience Design"... Experience! How in the world did adobe designed THIS experience for the designers?
Things like this makes this software literally unusable. After that uptade, i have to provide my client with hundreads of new links. This is utterly unprofessional. When is adobe team going to fix that?
Having this same issue with the way my team work.
My boss needs me to work with local files so we have a backup and a source file that everyone has access to incase I'm not available. After-all the artwork belongs to my company not me personally.
If the share link was saved as part of the file it would mean another team member could pick up a file off our network drive, make changes, and update the link. Currently if that happens a new URL is generated creating confusion with client and developers as they end up with multiple urls and can end up looking at out of date artwork.
If we use cloud files, and I invite another person to edit my file they cannot publish the link, they can only ask me to do that.
This is no good in a team when people work different days or take holiday etc.
And does not satisfy the need for locally stored artwork.
It would be great if the links were associated with the file instead of the user. My team uses local files instead of cloud and currently if 1 teammate creates links and puts their file on the server, then another teammate pulls that file down to make edits and the links are wiped out for them and they have to create new ones. This leads to a confusing and unnecessary amount of links.
Is this addressed? Its incredible annoying and it does not seem to be a solution anywhere...
I agree with all the comments below. This needs to be addressed ASAP! It would have been nice for a warning or if the link would have been saved to the file, even after renaming.
I just had this problem with a high-profile client. I got the approval for my prototype so I pulled the link to get it to my director ASAP (we were under a time constraint.) AFTER, I resaved my file (under the final version name) because it was approved and I like to stay organized (files build up fast.) Not knowing that since I saved it after it would delete the link, usually if you make an edit to a file and save it, those changes save to the file (so weird to think it deletes it?) where I can no longer modify that link...
So, now I will need to send out a NEW link, just in case I need to make small edits. This does not look good on me. I really wish there would have been a warning before renaming. Because I now do not have the original file where the link was located. I saved over the name.
Yes, I learned a lesson, save first under my final version name and then pull the link but I was in a rush to get this to the client. But a warning would have been nice and saved me the embarrassment.
Also, even to better improve. It would be nice, when you look at your "manage links" it can tell you the name of the file and where it came from.. or even have the file linked to the link. For quick access and editing so it is all saved in one location. I know that would be helpful for me personally, more ways to stay organized. Less time looking for old prototype files, with a link in it.
Similar issues. I normally have to move the local file into Dropbox for backing up reasons.
Soon as this happens the link is removed from the file.
Absolutely ruins sharing links and collaboration. Links should be locked to the file no matter what the name is.
This is why tools like FIGMA win over. This relinking mechanism is causing a ton of frustration for my team and the groups we support, because when a relink happens all the prior comments are lost.
Also why are you using percentages of a pixel Adobe! So annoying to have to shoot for accuracy when I'm .5 pixels off.
This has caused me a great inconvenience and now my entire team is getting confused about where to link to in order to see the latest design. Please allow us to choose old links to update.
Ivan Berka commented
Sure Phil and all. It makes sense to at least let the user know that “Saving as…“ would render existing (and used by many) links in new file obsolete. I vote for your proposal.
But I experience that XD wants me to create new link even for existing flows (with existing links) whose objects has been only edited. Up today I wasn’t able to track down which change triggers such a behaviour but it confuses me similar way.
Sarah Sorensen commented
My developers are so unhappy about new links for mockups. Sometimes I make a change to a file but some kind of update forces me to create a new link for that file. Then I need to figure out all the places that that link is mentioned in documentation so I can update it. I really need the choice to keep the original link and just update the file.
Patty B. commented
Please at least warn people when they choose "Save as" that this will happen. This created a huge problem for me. Now I have to go do a bunch of work moving my old comments to my new link.
Nadine Gin commented
If I create a file and share it with a link I am able to update the link.
If I move the file to f.e. OneDrive the already shared link disapears in the file. I can see the link in my overview but I have no possibily to reconnect the link to the file which is difficult for me if I already shared that link to people.
Need an ability to publish file to an existing link (for renamed or even replaced file)
PLEASE add the ability to use the original link, as well if using "save as".
Annoying workaround: if I want save XD-file under a new name I make a copy in Explorer and rename it there. Then the links are kept. I NEVER use "save as".
Still waiting on a fix to this, it's absolutely mind-boggling that it hasn't been addressed. It's such a major block to workflow, having to create a new link every time we to send to the client instead of just updating the current link (like how XD previously used the Save option) is ridiculous. Newsflash Adobe, not everyone wants to be forced to saving to the cloud.
Any Update on this? It's a daily problem for me and disruption to my workflow.
yes, i am in agreement with everyone here. I have sent out a document to many, many people and the link was shared in a newsletter. now i need to add a small edit to the document, but i have to make a new link. there is no way that everyone who received the original link will be aware of the new link!! this makes editing virtually impossible if the original document was shared widely and with no uniform way of resending the new link. Please please please change this ASAP. I need to make an edit to my document and retain the original link!!!!
I'm right with you I posted the below response to the Request that got this changed. "Share Again – don’t copy URL on Saved-As"
Elaine, this change is Bad. It's now more like a "save as new" not a traditional Adobe "save as". I place the shareable URL as an asset or resource inside what makes up an XD file.
Fundamentally "save as" is a complete duplicate of the file at that point in time, in every way with a change in the file name. Leaving all the work you just have finished safely in the original file. Giving optimization of file size, document cleanliness reducing layer and groping management, and versioning.
The option to create a new URL "Found in the share view" is plenty appropriate to split from an old URL with a new URL. The use cases of "I forgot to.." or "Bad file management" is not good enough in my eyes to change the "save as" function.
Now a little about why this is so destructive to workflows involving multiple teams in small, medium and large companies. Stakeholders, Product, front and back end engineering to QA, all need to be aligned with a few core pieces of any project. Requirements and what it should look and work like. You better believe the ability to have a single point of UI/UX truth becomes key to all staying on the same page as the project moves from start to finish.
The life span of a project can be short or very long. Evolving across departments leaving behind our sharable XD URL in requirements, Applications, and Notes. From Executives to Managers and other note-takers on a project the last thing they want to do is manage the UX/UI or Designers constantly changing URLs.
People naturally pass that sharable XD URL in all sorts of ways `slack, email, spreadsheets'' with the expectation they will not need another link until told explicitly otherwise… This lightens the load on my department to update in all locations that we may or may not have access too.
This has been key to the department's buying into, using and referencing the Adobe XD URL. The phrase “I have pushed the changes to the URL” has become super powerful and means the same thing to every department.
In true design fashion, I keep a complete archive of the project and process in XD files. The ability to start the one URL from beginning to end has been powerful in optimizing workflow through the life of the project.
If a file is the whole project or just a small piece of one, the decision is mine when I need another shareable URL and not stunted by "save as". I should be able to document my XD files my way without having to create a new URL for every file I save, till I create a new file.
Alternatively can we not give the option to reset the shareable URL during the action of Save as with the "never show again" option if this is critical to product functionality?
Thank you for your consideration, Please change this.
Aron Schmid commented
Please give us choice and till then return to the old way of handling links.
Make people use a certain workflow and then taking it away from them withouth asking is a no-go, I think.