You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Microsoft 365 can't save edits on files from Dropbox - Android
I can't edit excel files stored on Dropbox from my Android device. instead of saving the edits, a new file gets created every time I save the edited file. this is what happens: 1) I open Dropbox...
Hey Hannah, thanks for your reply.
I downloaded a standalone Microsoft Excel app and it solved my problem! using this app I can now save edits of files stored in my Dropbox.
I didn't have the Excel app before, as I was using Microsoft 365 app which can handle all Microsoft files (Excel, word, powerpoint...).
if you want to continue debugging the problem with the Microsoft 365 app, I'll be more than happy to help. I opened an Excel file stored locally on my phone via the Microsoft 365 app, edited and saved it. it didn't save the changes directly but asked me to save a copy and, unlike files in Dropbox, I successfully overwrote the existing file without new file being created.
Clearing Dropbox cache didn't solve the issue.
Most probably it's a bug with the Microsoft 365 app.
Hannah
Dropbox Staff
Dropbox StaffHey kankon, thanks for bringing this to our attention.
Are you having this issue when opening Office files only through the Dropbox app?
If you open an Office file that's saved to your device directly through the Excel app, for example, are you seeing a different behavior?
And if you clear the Dropbox app's cache from the settings, does that help?
Let me know and we'll go from there.
Hey Hannah, thanks for your reply.
I downloaded a standalone Microsoft Excel app and it solved my problem! using this app I can now save edits of files stored in my Dropbox.
I didn't have the Excel app before, as I was using Microsoft 365 app which can handle all Microsoft files (Excel, word, powerpoint...).
if you want to continue debugging the problem with the Microsoft 365 app, I'll be more than happy to help. I opened an Excel file stored locally on my phone via the Microsoft 365 app, edited and saved it. it didn't save the changes directly but asked me to save a copy and, unlike files in Dropbox, I successfully overwrote the existing file without new file being created.
Clearing Dropbox cache didn't solve the issue.
Most probably it's a bug with the Microsoft 365 app.
- Nancy
Hi kankon! I hope you’re doing well, and thanks for your feedback.
You mentioned in your first post that you received an error message at some point when uploading the updated file (“Upload failed: ABC_19RandomNumbers.xlsx (tap for details)”).
If you’re also receiving this error message when uploading other files to your Dropbox account, let me know and we can have a look into this.
Hi Nancy , I'm happy to let you know that the problem have been resolved with the Microsoft 365 (office) app as well 🙂
Some context:
After I installed the standalone Excel app, there was an option to link the app with cloud storage providers. from the list of providers, I choose Dropbox and it was linked successfully and I was able to edit and save Excel files stored in Dropbox.
After your post, I decided to check Microsoft 365 (office) behavior with other files. When I opened the Microsoft 365 (office) app, the app automatically re-linked itself to Dropbox. so now when I hit 'open' or 'save as' icons, Dropbox is directly listed in places I can open files from / save files in.
Previously, the app only allowed OneDrive to be directly listed in the 'open'/'save as' page. To access Dropbox I had to touch 'Browse' and choose Dropbox from many other possible location such as local storage, Google drive, Dropbox...etc.
After the re-link, when I tried to edit and save an Excel file from Dropbox, it still doesn't save the file directly and ask me to 'save as' the file. But now, when I ask it to overwrite the file, the app successfully overwrites it. no ABC_19randomnumbers.xlsx file is being created now.
It's clearly a Microsoft bug
