Forum Discussion
Sharepoint differences in opening Excel files
jm_herard although I appreciate your reply, it doesn't answer my question. Both files are being opened from the same location (inside Teams on a Sharepoint page from a quicklink). So it isn't about the way of opening it. The files are all excel files opened from a Sharepoint page quick link in teams and they behave differently.
DhirenMehtaMSFTMicrosoft
dblemker I did some testing on my lab tenant and I have partially noticed the same behavior that you have described. However, few things to note here.
1. In my case, when I am using QuickLinks web part on the SharePoint page, All the Excel/ Word/PowerPoint files are only showing Catch up button and NOT the Close button. This is because when you use QuickLinks web part, and click on the Link on the page (from the Teams client), it's loading the Link as a whole page in the Teams client. (This is the same behavior you will see when you will click on the Link from the SPO site in the browser directly). Also, you will notice in this scenario that the URL of the Page doesn't change (you can use Fiddler or web version of Teams in the browser to notice this). This means that when you are using QuickLinks web part links in the SharePoint page and when you are opening the SharePoint page from Teams client, Team client is simply opening the link as a new page (like how you would see in the browser).
2. However, When I have Document Library web part on the same SharePoint page and when I tried to open the Excel files form the Library web part in Teams client, I can see the Close button and also, the Excel file taking over entire Teams client real estate (as you have mentioned). This is because when you are opening the file from Document Library web part, Teams client is using DOCX/XLSX Viewer Web/App Part Functionality to display the file and this Web/App part seems to have Close button in it. If you open the teams team in Browser and click on the Excel file from Document Library web part on the SharePoint Page tab, you will see the URL pointing to something like this. https://teams.microsoft.com/_#/xlsx/viewer/teams and also look at the browser tab title changing with something like "XLSX File Viewer | Microsoft Teams"- So from what I am seeing based on my research and testing, the behavior you are seeing is currently by design. However, if you are seeing these two different behaviors using the QuickLinks web part itself, then can you please provide detailed repro steps and some screenshot to better understand the scenario?
DhirenMehtaMSFT Thank you for this. I thought you were on to something... but alas I don't think so. I'm going to try to share as much as I can about the files without violating our company policy with information sharing.
The Sharepoint page loading within teams as our "Main Menu" of sorts is made up of multiple web parts with quick links. I used the browser version of teams to get the links for you as you suggested. One section of the quick links opens an excel document as this: https://teams.microsoft.com/_#/xlsm/viewer/teams
The other part opens excel files as this: https://teams.microsoft.com/_#/tab::1a097827-23d1-4415-b11f-fca99483ccb4/General? (within continuing thread ID information that I can't paste without it renaming it).
The weird thing is, all files were added the same way: Add Link>Site or Add Link>From a Link. Both options respond the same way. But for some reason, the few files react differently and come up as the xlsm viewer. I don't know how to force it to load it that way. None of my elements are document web parts (that I know of). Everything is set up as quick links.
- DhirenMehtaMSFT
Thanks dblemker . Based on your response, I still feel that the First excel document that's opening up is Not Quick Link but without actually looking at it with screenshare, I don't have any other ideas to offer. Only other thing I can think of is you can edit the page in SPO site in browser, Delete the "non-working" quick link and re-add it to see if you are seeing any difference in behavior. Be sure to publish the page after the changes are done.
Can you open up a Support ticket with our Teams team so that Microsoft Support team can work on this with you?
