0

I’m using the excel importer. There are multiple decimal fields and one column “TicketDate” is a date time, but I’m storing all the values as strings, because instead of failing with an ugly message if there’s a problem, I want all the correct rows to import and I’m doing some custom parsing with error handling to let the user know which field there was a failure. I mimic my “Ticket” entity with a “TicketImport” entity, making all fields strings. Loop through each TicketImport, parse the fields in a custom way and then create a Ticket.   In excel I have the date field for some rows as ‘12/1/2022’ (I’m American, I know… we put the month first). Keep in mind the object is the TicketImport entity where everything is a string. When I debug, I can see that the imported value was automatically changed to ‘12/1/22’. It seems to AUTOMATICALLY convert the year to 2 digits, even though it’s just a string.    I do an error check to make sure it’s a date. If it fails, I alert the user. If it passes, I use the following expression to store into the ACTUAL TicketDate field of the REAL entity:   parseDateTime($IteratorTicketImport/TicketDate,'MM/dd/yyyy')   The date that gets saved? It’s “12/1/0022”   First off, I’m not sure why its converting the ‘12/2/22’ to ‘12/1/22’ on the import. I assume it’s someting weird with Excel. BUT… You would THINK that the parseDateTime function in mendix would save it as 2022 properly. It isn’t. It’s saving the year as “0022”. Does anyone know why? I’m trying to have to avoid string parsing and concatenating “20” to the front of the year.

asked 2022-12-08

1 answers