Problems with date conversion on free cloud node

0
I'm not sure since when it happen, but have the idea that the problem started while publishing the app from 10.18.0 to the free cloud.  It's the line parseInteger(formatDateTime($kalender/Datum, 'yyyy'))in a before commit event on the kalender table that has changed behaviour. It gives the year in 2 digits instead of in the requested 4 digits: so a date in 2025 gives 25 instead of 2025. It worked fine in the past and still works that way in the local development environment. See the screen shots (order: local, event, free cloud).Any idea how to fix this that it starts working as it should again  in both environments? Or is it a setting in the free cloud? Am I  able to fix this in that environment and how?      
asked
2 answers
1

Hi Peter,

 

Date formatting is configured per language in an app. Have you checked if you have configured the right formatting for each languages you have? You say it works fine in local app but not in the cloud app. Do you you use the same language settings in cloud app as in your local app? This looks like a language problem to me. 

 

image.png

answered
0

Date format was set correct, Time format was set correct. 

Date and time format was empty. (and now also set). 

Only one language is set: Dutch Netherlands also set as the default language.

I've created a microflow to empty the complete table, now it works fine. 

(Might also bee that old data was shown up).

 

Thanks for the tips

Kind regards

Peter

answered