Excel App opens old Version of document saved in Sharepoint Online

[DaveZ2022]

I am not quite sure if It's a sharepoint online or an excel problem. If I open the excel document with the online excel version, it will show me to correct last saved version of the document. If I open the document with the app (excel program on my computer) it shows me an old version with the hint that there is a new version on the server. Any suggestions inside the program to solve the problem don't work. It will still open an old version. 

Do you have any suggestions for me?

[#2]

Sounds like a file sync issue. Do you have the library sync'd to your local computer? Check the OneDrive client to see if there are any file sync issues.

What happens if you right click the document in the Browser and choose Open with App? Does that open the correct version?

[#3]

The file (library) isn't sync'd to the computer. When I click the document in the Browser and choose Open with App, it will show an old version, when I choose open in browser (the online version of excel) then I'll see the correct version.

[#4]

Hi, I have the same issue. Was it solved? For me it re-ocurring  with some files.

thanks

[#5]

I have the same issue. I have tried many things to fix this but cannot resolve this. I need to be able to open this file in the app because the filters in the browser show limited results and this hinders me from finding errors. I need this resolved so I can open the current file in the app. Thanks in advance for finding a solution.

[#6]

This resolved the issue for me. I had to open another Excel file to do this and save, since my messed up file could not be saved.
https://www.mrexcel.com/board/threads/working-from-sharepoint-cache-issue-discard-changes-fix.116321...
Here is the text from the post.
"Hi Luke777, hope your issue had got resolved. I had faced exactly the same issue. It needs Office Document Cache to be cleared in order to fix this which is available from File --> Options --> Save --> Caching Options. Checking the box " Delete files from the office document cache when they are closed" fixed this issue."

[#7]

@GernDog thank you so soo much! That helped me too :) 

[#8]

@GernDog is the man, this helped me out too! 

[#9]

@GernDog thanks for this, worked great for me

[#10]

In my case Excel was opening the previous version of the file. Luckily Excel also showed a security warning, whose details could be seen in the File->INFO section. One of the warnings was that there was a newer version of the file on Sharepoint, choosing to open it fixed the problem

[#11]

Thank you for sharing. This has been bugging me for AGES, I just had another Friday afternoon look to see if I could find a solution, much appreciated!!!

[#12]

Thank you GernDog. Your suggestion to use Word's File --> Options --> Save --> Caching Options. Checking the box " Delete files from the office document cache when they are closed" and then pressing the "Delete" button ............brought to a successful conclusion 6 hrs of stumbling around by me. I had a Microsoft Access application that created a Word Doc from a .dotx template. For some reason -- apparently caused by the template when creating a "new" Word doc, finding a cached version that was a .doc, not a .docx. This seemed to somehow -- when the VBA code was using this .doc to save it as .pdf, so as to attach the.pdf to an Outlook email -- trigger a message from Microsoft saying "This file type doesn't support Microsoft Information Protection", and the .pdf was not created. I don't really understand why the "File --> Options --> ...." set of choices mentioned just above .... seems -- after quite a few now always successful tests -- to have solved the problem. By "solving" I mean that opening the .dotx Word template, ever after that above-mentioned set of instructions was issued and its final "Delete" button clicked, create a .docx file rather than apparently open a cached .doc file. Then the subsequent instruction from the .docx file to save itself as a .pdf succeeded. Previously, in at least a dozen tests with carious workarounds, it had always failed.
Thank you.