Skip to main content

We have some tables with start and end dates per row. When we do an export we see that all dates are no longer in the format that we used in the app. In Universal we use dd-MM-yyyy and the downloaded file uses MM-dd-yyyy.

We would like the export function to follow the date representation that the user within the application has.

NewOpen

We have some tables with start and end dates per row. When we do an export we see that all dates are no longer in the format that we used in the app. In Universal we use dd-MM-yyyy and the downloaded file uses MM-dd-yyyy.

We would like the export function to follow the date representation that the user within the application has.

Especially when adding rows (and re-importing) the file this is an issue. The date shown in the cell is different then the one shown in the "formula bar”. So when adding new rows and typing the date (following the cell above) you get the dd-MM part wrong and import the wrong date.


Are there any updates on this?


Hey @Anne Vries,

We also have a ticket in TCP with the same wish which has already been placed on the backlog, so I'll update the status of this idea. Indicium will be working on some more Date related stuff which may relate to this idea. We'll make sure to link them together. Once the ticket, and thus this idea is worked on, we'll be sure to update the status.


OpenOn the backlog

Hi Mark, we experience the same problem as mentioned above. Export of dates with format dd-mm-jjjj from UGUI 2025.1.14.0.0 gives in Excel a visual of mm-dd-jjjj although the value of the cell is correct. So it seems to be a display issue. 
Do you have an update of the last status ON THE BACKLOG ?

 


On the backlogWorking on it!

We’re working on proper support for Localization settings with Release 2025.3, and we have decided to include a fix for the Excel export of dates and numbers as well! More details on other Localization settings can be found in this Idea:
 

 


Working on it!Next release