> Convert a continuous string of letters and numbers to a date.
This has been a massive bugbear of mine. Particularly when it inexplicably chooses USA date formats even when faced with a column containing values like 15-07-75. It would frequently convert half the values into US date format where possible and leave others like above unconverted.
Yes, I had big issues with Excel converting a number range like "1-3" to "3rd January" when importing property data. Eventually switched to Libre Office which works much more intuitively.
And leading zeros, which is awesome when postal codes have them and shipping software uses csv imports. Somebody only has to open the file once, and it isn't immediately obvious unless people know to expect that.
I used to work with some data that would come across as CSV files but from non-technical people and required leading zeros on some fields. Trying to explain the difference between csv and excel ... or why you should not open those files in excel ... was difficult to say the least.
CSVs need an option to open as text.
Or at least to tell people "hey, there butchered your data for ya" with an undo option.
I got a ticket from IT dept (lol) that a CSV is the wrong format. It wasn't.
This article says the user will be notified if any data is automatically converted when opening a CSV. This should have been done a decade ago but I'm still glad to see it.
US data formats, REGARDLESS of any regional setting you might have for dates. So even if they were dates being auto-formatted, they were still doing it wrong.
Anyone done this? Open a .csv in excel to fix/edit a item, then save it without realizing that it autoformatted a bunch of columns. Now it doesn't work in the parent program anymore.
Excel isn't the only MS product with US date insanity. Outlook set up for AU region only supports date filtering in searches using US date formats, which is the icing on the turd sandwich of date searching as Outlook requires you to hand write in text search queries to search for before/after x date.
This has been a massive bugbear of mine. Particularly when it inexplicably chooses USA date formats even when faced with a column containing values like 15-07-75. It would frequently convert half the values into US date format where possible and leave others like above unconverted.