11-03-2016 05:34 AM
11-03-2016 05:34 AM
First, I want to say Amazing Job on the release of Microsoft Teams!
We just had our go-live for O365 this week after migrating from Google Apps. I have been frantically looking for something to fill a gap that we have stumbled across that we were using on GApps that doesn't exist in O365. Then along comes Teams and has promise to give us much more than plugging the gap that I have that is frustrating our users.
The Chat Bot told me that SharePoint Document Libraries (although you can add it as a tab in Teams) isn't quite ready. (BTW, I love it when a Chat Bot actually answers the question that I ask it!!!!) Having the abiltiy to link a document library from SharePoint into Teams will plug the missing feature that we relied on in Google Apps. Do you have an ETA when this integration will be ready? I would be very much willing to test this out with my user base. This would, IMO, be a game changer on user acceptance of our O365 rollout.
11-03-2016 05:55 AM
Yes, having the ability to link Sharepoint document libraries to Microsoft Teams is exactly what I'm looking for and what is missing for my organisation in Slack. This would be very helpful!
11-03-2016 02:26 PM
11-03-2016 04:11 PM
11-06-2016 05:17 PM
11-06-2016 05:17 PM
I tried to add (pressing "+" in tab) Sharpoint site to channel both in Teams web and desktop apps. Both give me the same problem. If I select one from "Relevant sites" and click "Next", there's no further response. If I enter the URL from "Use a Sharepoint link", I get an error message saying "We couldn't find any Sharepoint site or a folder. Check the link and try again."
Teams desktop version: 0.6.00.30201 (64-bit); last updated on 11/3/16.
11-06-2016 08:38 PM
Is one of those bugs the situation where you try to add a Documents library that isn't the default 'Documents' one and it says that it works but it adds a bugged copy of the 'Documents' library instead?
11-07-2016 06:57 AM
11-07-2016 02:03 PM
Based on the descriptions a few of you have provided it sounds like there are likely several bugs involved. I'll have a support engineer from our team reach out to you individually to collect logs and other information to assist in our debugging.
Thank you again for reporting the issues, and we greatly appreciate the assistance in identifying the root cause.
11-07-2016 04:51 PM
Thanks Kyle, If this bug is fixed and the option to choose the columns to display in the integration is added, I can see this being huge.
11-09-2016 01:59 PM
FWIW, I too am having problems with SharePoint in Teams. The error I receive is, "The Files are no longer available". I've seen elsewhere this may be related to a bug with libraries that have spaces in the path name.
I test almost every day so am intersted in knowing when this gets fixed so i can roll out Teams to my users.
11-12-2016 01:08 PM
Absolutely. I would like to be able to have a custom document library available in a channel in the event the collaboration is specific to content of a particular existing library. Seems it list the custom documetn library and adds without error but then its actually adding the default shared documents library. A true but that I'd like to see corrected.
11-29-2016 06:38 AM - edited 11-29-2016 10:40 PM
Hi, I've started using Teams and wanted to add my default root document library, but I get the message "These files are no longer available. Check to see if site is available and try again".
I've went through the add tab wizard > sharepoint > it even suggested my connected Office 365 Groups site > I select the Library > give it name > click save and done. Except, no files but the message above.
The Group uses the "German" locale, so the URL is something like https://tenantname.sharepoint.com/sites/o365groupname/Freigegebene%20Dokumente/ (I still don't get why Microsoft insists on changing default library names to german, instead of leaving them in english...)
11-29-2016 11:31 AM
Alan, this issue (adding non default library) has been fixed in the current build 0.6.00.32301. If you are still experiencing after updating to this build this please let us know.
11-29-2016 08:34 PM
Where is the build you mentioned?
I have run updates and reinstalled only to be at Microsoft Teams Version 0.6.00.31001
11-29-2016 08:57 PM
11-29-2016 08:57 PM
Settings | About shows "You have Microsoft Teams Version 0.6.00.31001 (64-bit). It was last updated on 11/30/16."
11-29-2016 09:58 PM
First of all, Kyle - thanks for bringing in the SharePoint document library integration already in the beginning of the preview.
As someone who is accustomed to finetuning the inner workings of a SharePoint library, I've got one question though: Is the support for different views within SharePoint Document Libraries and / or document metadata on the roadmap to be added to the SharePoint tab? Or do the users have to navigate to the actual SharePoint library view even in the future to achieve this?
11-29-2016 10:19 PM
11-29-2016 10:43 PM
@Rebecca Valdivia wrote:
Can you confirm that you have the current client version, 0.6.00.32301?
Same as the other replies above.
You have Microsoft Teams Version 0.6.00.31001 (64-bit). It was last updated on 29/11/2016.
I would have assumed to get the latest version, since I only started using the product yesterday and downloaded the setup fresh from teams.microsoft.com. I've also manually checked for updates it says I'm on the latest build.
11-30-2016 01:05 AM
Yes, I can confirm a version 0.6.00.31001 (64-bit). It was last updated on 11/29/16.
Another point I really don't like is how the version is displayed. (UX) I was really expecting, that some kind of dialog will be displayed, when I click on "About " and after few try I founded, that the version is displayed on the top of window.
On the other hand, I really like MS Teams and idea behind it. It will need some improvement and bug fixing but it looks really promissing.
11-30-2016 05:17 PM - edited 12-05-2016 05:28 PM
The update is pushed out over different rings - so may not have made it to your tenant yet. Version 0.6.00.31001 is the prior version even though it says you were updated (a fix for displaying that you were updated when you havent been should be in the next update). Some of the SP file issues in this thread have been resolved in builds after 0.6.00.32301 (0.6.00.32302 on Mac). You may want to manually check for an update again periodically.
12-05-2016 02:56 AM
You can sync documents from any SharePoint library (on-prem or Online) with Teams documents, also from local file server department shares or user home drives via 3rd party tools like the Layer2 Cloud Connector one-way or two-way with flexible options.
12-05-2016 07:02 AM
12-05-2016 05:30 PM
You have the current build (I revised my post as I referenced the Mac version). I will reach out to you directly on your issue.
02-10-2017 12:35 AM
Why is Sharepoint Integration not working?
The default sharepoint site for the Teams group I created inside MS Teams won't find documents:
02-10-2017 02:58 PM
I did create a support ticket and wanted to post the results here too. Apparently, you cannot just add a sharepoint site. Even though you select the actual document library you want to sync with the team, it will just not show up.
What did work was uploading a file into 'Files' in Teams which would pop up in the sharepoint teamsite that was generated when creating the Team. From then on, all files that were added to that folder (called General) were being synced back and forth between SP and Teams. Not great, but at least it is something...
02-26-2017 01:20 PM
Thanks for sharing that Vincent.
The question remains though is (for the MS folks) - we have many teams which rely on existing processes which provision an internal SharePoint site - which is different than the "internal" SharePoint instance for the team created by Teams. The SharePoint connector should be able to surface the files from the existing SharePoint deployment as well. Is this something currently being looked into, and is there anything we can provide (logs, etc.) to help in that investigation? I can repro the problem with our instance as well (SharePoint on-prem document library).
03-03-2017 08:04 AM
I just started using teams after having used Office365 for a couple of years. In that implementation we have several sharepoint sites and existing document libraries that I'm tring to make visibile in Teams. In one instance I was able to use the '+' to add a sharepoint site by providing a sharepoint link to the existing library. That worked for one instance where there is only one document library on that site.
I tried to do the exact same thing to a site that has several document libraries on it. In that process I was prompted to select the specific document library I wanted to include on my Teams general channel and I received the message 'We Can't get your files. We're working on getting them back.' Huh? What am I suppose to do? I don't really want to link/sync the same documents into two document libraries. that seems pointless.
Any thoughts? is this a known issue?
03-03-2017 10:12 AM
Greg, you should be able to add libraries from sites with multiple. Sounds like this may be a bug. We just had a new update release this week, so please update your client or session first and try again.
I'll have a support member from my team pre-emptively reach out in the case that doesn't work and we need to debug the problem.
03-07-2017 11:27 PM
Hallo, we have Microsoft Teams Version 1.0.00.6501 (64-bit). The issue with the sharepoint tab described above is still present, no files are shown in that tab, with the message "We can't get your files. We are working on getting them back".
It would be nice if this would work.
03-09-2017 03:37 AM
That's pretty strange because I have a same version and by me it's working now. It was not working but I tried it few weeks back and I was succesfull.
From which region you are? The reason of question is that I saw somewhere (maybe in this discussion) that some feature of MS Teams are released in some sequence by countries, regions or something like that. But now I'm not able to find this source of information. So I'm not 100 sure I'm right. Maybe you just need to wait little bit.
03-09-2017 06:24 AM
I'm in the US. We use Office 365 and have a main site for our company with many document libraries on that site. Here are some screen shots that I just took trying this again.
03-09-2017 06:56 AM
So in that case please try to ask somebody from MS Teams's support Team. I had before same issue but not anymore.
03-09-2017 09:07 AM - edited 03-09-2017 09:07 AM
I have already reached out to those of you with an exisiting issue via private message (here on tech community). Please gather the requested infromation and send that info to me so we can investigate your issue(s). Thanks!
03-15-2017 01:02 PM
same issue here. Can seem to add SP document library on MS Teams app. I'm on a mac by the way
03-16-2017 11:02 AM
Thank you for providing logs and assisting us with this issue. With your help we've narrowed down the possibilities, but need to make changes to our telemetry to find the root cause. The changes are already on the way - I'll provide another update based on the results.
Thank you for your patience!
03-16-2017 08:32 PM
03-16-2017 08:54 PM
04-07-2017 12:07 PM
I have the same error:
04-12-2017 01:29 AM
06-01-2017 07:16 AM
I'm having the same issue when using Teams. I create a Team, then click the Files tab and encounter the error.
I've been told "wait 24 hours" on a similar issue - with the idea being that "behind the scenes, Microsoft is provisioning the storage" and it can take up to 24 hours for that process to run.
#1: the error message should be more descriptive
#2: this error never should happen in the first place - come up with another way to provision file space if this is really what's happening. Nothing like having work interrupted.
06-14-2017 09:04 AM
when adding sharepoint tab to teams channel, Is there any way to select specific path from documents instead of the whole document tree? That would be great!
Our proposal is to keep every project document in the sharepoint site instead of the teams file tab in order to keep it all together.
Thanks in advance!
06-19-2017 06:53 PM
Are there any remaining known issues with linkage to SharePoint?
We are in a hybrid situation - most of our SharePoint is at O365. We do have a few sites on-prem. I am unable to link to these on-prem sites.
"We couldn't find any SharePoint site or a folder. Check the link and try again."
Is this supported?