Links/attachments in chat
If you attach an item to a chat it will be saved in the files section of the channel. But if you are chatting about a document and you want to reference it you do not want to save it to the channel as it is already in another folder of the SP Site. To create a copy in the channel does not make sense as you are creating duplicates. a link would be the solution.
This feature is still in the works. No additional details are available at this time.
In chat I am missing an easy way to crate a link to a file.
Linking to file should be simple where the link-text is the filename.
Today you first need to "copy link to file" and then press CTRL-K (for link) - and paste the link in URL, but you manual have to put in the filename. It is not possible to copy it from the link as it contains %20 for spaces.
It would be even better if the link is technically implemented as an object with uniq ID so any update to filename or url will be reflected
(I wunder why this is not standard now-a-days - I can remember it was standard in IBM-OS2 in the last century:-))
Richard Adam Boettcher commented
Internally, our company is comparing MS Teams with Slack to be able to easily link share-point sites/one-drive/channels and mention files within the MS suite of products and remove cross documentation duplication would be great!
Richard Adam Boettcher commented
Can anyone update the status? Currently we have "Working on it" for last 8 mothns.
Any progress? Its the one major we still use Asana instead of Teams
Robin Dieker MSFT commented
any update on this? Please contact me via my V-Dash.
All the best
I'm trying to roll out Teams across our workplace and have just stumbled upon this issue after noticing that a shared file didn't link in a chat group. Rather annoying. Any update?
Any updates? Six months later and lots of silly gifs all over the place.
Turd Ferguson commented
There needs to be the ability to turn this feature off and/or filter certain file types from being 'saved' to the Files section when posting in chat; I constantly have to clear out all the silly gifs and memes and things that people link - and telling them not to do that isn't the answer - we need the technology to work for us not the other way around.
It should be possible to link to files in other SharePoint sites within the same tenant. If you fore example have site for document that are relevant for all in the firm, but a team want to link to it so they easily can discuss the contents. Now it will make a copy in the channel, therefore the team might be missing when the document is updated.
Monte Achenbach commented
At a minimum, if Teams is supposed to be a collaboration tool, Sharepoint should be an attachment option in Chat. Now you have only OneDrive (personal files) and Upload from Computer as options? Not seamless or intuitive...
That's a shame 2 years and still working on it!!!!
I have just discovered this as well - I would like to link a file on our server with a path url
[Deleted User] commented
+1 to "mention" (link to) a document that is already sitting in a standalone tab, although we understand you love creating duplicates with OneDrive track record (:
Werner Faber commented
Links occur on MS Teams, but we haven't figgured out why.
This happens without any comment, the user who causes them doesn't even notice it at first.
Would be nice to know under what circumstance Teams will add a link to a document stored in the team as a new conversation to that specific team.
I know one can add a link intentionally, but then one has to acompany the conversation with a comment.
This does not occur with the entries we are seeing.
It almost looks like Teams logs that user X has altered the linked document, but not all changes cause the link addition to occur. So this is not consistent.
For our company it is a key feature that a network path to a file or folder in a chat post is "clickable" (Skype already has this feature).
Any progess on this? Should be able to start a chat about documents from meetings and 1-1 chats that do not store a copy of the documents
Peter Rosenberg commented
Thanks, and File URLs (assuming the notation : \\server\<sharepath>\<file>.<filetype>
would be of great importance.
There is a very importance nuance in this one: we need a way to have items you attach to a chat be uploaded to an existing SharePoint Document Library, NOT in the default site SharePoint site that was automatically created when you created the team.
This relates to all people who do not want to use the default site SharePoint site that was automatically created when you created the team, including the following Uservoice submissions:
This also breaks my workaround detailed below.
Here is my use case, which I suspect others are facing as well:
* I don't want our users to save their files in lots of different SharePoint sites, which makes it harder to find things. I want them to save their files in our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically (accessed through the Files tab in teams)
* We have already created and used for years an awesome SharePoint document library with a taxonomy managed metadata and views everyone loves
* Therefore, in Teams, I want users to only be able to upload files to our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically (accessed through the Files tab in teams)
Here are the problems I faced that Microsoft could fix, and the workarounds I did to get it to (kind of) work the way I wanted it to -- you're welcome, Microsoft Team users :)
Problem 1: When I add our existing SharePoint document library in a tab, it does not include the fields and metadata I need.
Workaround 1: Create a new tab not as a SharePoint site, but instead add it as an ordinary website, and put in the URL of your document library. (The UI is not ideal, since there is a left hand nav bar in teams I have to do more scrolling to the right to see all of the SharePoint Document Library view, but at least we can access our views and metadata.)
Problem 2a: I can't hide the default File tab. This means that, instead of going to the new tab I created above to get to our existing SharePoint site, some users will see the files tab and upload file to it, leaving a mess ("wait, did I add the file to my new Team file area or to my existing SharePoint document library?")
Problem 2b: I can't change it so that, when you click on the default Microsoft Teams File tab and upload a file, it actually gets saved in our existing SharePoint Document Library instead of the automatically created new Microsoft Team site.
Workaround 2: In the Team File area, I add a link that goes to the URL of my existing SharePoint document library. I name the link "Use this link to the place to save files." I think click on the top nav bar item Open in SharePoint, and from there I clicked on Site Permissions, and set Site Members' permissions to Read-Only.
Result: Users save their files in our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically when I created the team, and users have full access to the taxonomy, metadata and views they already know and love from their existing SharePoint site.