18-01-21 02:27 AM
The process I'm working on exports a CSV file in which the bot will copy the whole worksheet and paste the table from the CSV file to a new blank xlsx file. The csv file contains columns that has dates in mm/dd/yyyy format. When copying and pasting the table, these date values reverse from dd/MM/yyyy to MM/dd/yyyy. However, when checked, both CSV and xlsx date values are still identified with the same numbering format, dd/MM/yyyy, although the dd and MM have flipped.
I noticed that this is only applicable when the bot cannot clearly differentiate the dd and MM. For example, 20/12/2020 will be clearly as dd/MM/yyyy format as there is no 20 for month. We had tried changing the Windows language and number formats to English (UK) and English (Malaysia/local) because there was a discussion suggesting that the blue prism MS Excel VBO is using English (US) with date format MM/dd/yyyy but it still didn't work.
Please let me know if anyone has a solution to this. Preferably I would want to avoid going into code stage level.
19-01-21 10:02 AM