No more warnings about saving as CSV, especially when I didn't change anything
I don't know how many hundreds (thousands?) of times I've told Excel that, yes, I really truly do mean to save this file as a CSV. I recognize that not all users will understand that CSV doesn't do cool formulas or formatting, etc., but I do and I still want to do it. And I want to do it a lot. Please, give me a way to opt out of these useless warnings!
We’re done – you should no longer get a warning dialog about data loss when saving a file as CSV, as long as the file was originally opened as a CSV file.
Instead, we’ve added a non-intrusive business bar (that you can ignore if you choose) that let’s you quickly Save As the file if you have made changes that are not savable in CSV; if you ignore it and just Save, we’ll just save out the CSV values as you’d expect.
We actually rolled this out starting on August 13, 2016 with build 16.0.7167.2040 for O365 users. Later builds have this update as well of course.
Thanks for participating in UserVoice – we definitely value your input. You can now use whatever votes you’d allocated for this idea for other ideas.
= started status 2016-06-15 =
Great news – we’re working on this (for both Windows and Mac Excel)
Thanks for the suggestion Tom, and thanks to folks for voting! We’re listening to you all, and we’ll get someone to take a look at the flow here. We’ll loop back and update the status appropriately.
John [MS XL]
David Aldred commented
You can disable / re-enable the warning by going to File-->Options-->Save-->'Show data loss warning when editing comma delimited files
So where in the program do I turn off the warning? There is nothing here that tells a user how to do it!!!!! If the solution is creating a macro, that is BS. There should be a simple checkbox in the save options to turn this off or on. WHERE IS IT?
Where is the business analyst? There needs to be a happy medium. Regular users need to be warned they are working in .csv so they don't loose data (arguably, they should not be working in csv in the first place), and developers/techs need the .csv save feature to be less obtrusive (you are prompted no less than 4 times, twice on initial save, and twice when trying to leave the document, even if there were no changes!). The balance is to notify the user upon initial save and then alter the UI when working in .csv. You currently can keep working in multiple tabs, even though you are in csv. This is dangerous for normal users and developers alike. A good balance would be to alter the appearance of non-active tabs or remove them completely upon save (or maybe provide a toggle to "work on at your own risk," after having prompted the user that .csv mode is being implemented. The irony of all this? This problem has persisted for years and MS still had not implemented a common sense solution. Again, where is the BA?
This **** is so typical of Microsoft - the worst software company on earth. My Christmas wish is for this company to go bankrupt.
Just lost few hours of important work due to this. No warning what so ever, while saving or creating / adding "xlsx" features into original CSV file. Either it should not allow to add these features, or give warning before saving as CSV. And it seems there is NO way to recover it either (from a .temp file etc)...
It almost cost me my job due to work on critical data on critical timeline.
Very Bad idea.
Robert Bradford commented
I'm still getting these warnings when saving as a .csv and .txt file in Excel 2016. How can I turn them off? It's already multiple clicks to get to the save as command and then more clicks to get the application to respond as I intended.
Just lost 3 hrs of work b/c added macros to a .csv file that I did not know was a .csv file.
Programmed the macros. Saved it. Got no warnings. Opened it back up and, classic, all data was in col A and all the macros are gone.
Help? I need the warnings back!!! To loose 3 hrs is gut wrenching. MS didn't just throw out the baby with the bath water on this one, they threw out the whole bath tub. (This has happened to many people as you can see in the above posts)
At the very least (since MS is about as responsive as a dinosaur bone), does anyone have a workaround?
Removing the warning is wrong, I just lost 4 hours of work on other tabs, because I saved as a CSV (the file type I opened). Add a warning that you can disable if you don't need it, don't remove the warning altogether.
Hours and hours of work lost because there is no warning. This was a bad idea.
Yep, you have just cost me three hours work by only saving one tab of my spreadsheet because I based it on a CSV file. Thanks for that. A warning would have been really, really nice.
Aaaargh! I liked it how it was
Chris Ford commented
Unintended consequences, now Excel doesn't ask at all. Previously if I opened some form of txt file Excel would inform me of data loss on save and provided a simple option to rename with the xlsx extension. It no longer asks, and I have to type the entire name when I do the save as. This was not an improvement. I have lost data countless times and am frustrated as old habits die hard. Please correct this.
where is the "non-intrusive business bar that I can ignore" ?
@Andy just use a macro activeworkbook.saveas FileFormat:=xlCSV Filename:="yourfilenamehere"
In Excel 2016 for the Mac, there is an option in the preferences to show a warning when editing CSV files. This is the perfect way to deal with users' different needs, but -- I'm not sure if the warning has been hidden somewhere that I haven't noticed, but the pop up I was used to has disappeared. It saved my butt many times, and I leave the preference checked -- but I still don't see any warning. Is this a feature "in progress," is the warning less visible, or what?
Not fixed. I use a .xlsx file, edit it and save as a .csv for a third party, to produce mail labels. Quickbooks at one side, Royal Mail at the other and little me in the middle getting really fed up with the whole beep and warn **** 20 times a day.
I get it, I have read the warning, please, please, please let me turn it off now
Scott Owen commented
Ok...so....as long as you're in the "make people happy" mode...
any chance to making a true "double quoted" (all columns) CSV (without messing around with VB scripts)??
I know...the RFC is "vague" (at best) and "stupid" at it's worst points......but still .... it seems the "proper" way to do things.
Matt Szmaida commented
yay! thank you!
Taylor Murphy commented
Wonderful! Thank you all so much!
Wow, only 8 months before MS responds to users! so fast!