Hi,
I just reported this bug here https://github.com/microsoft/AL/issues/7160 But I'm a bit pessimistic that they might just dismiss it as they closed all the channels to report bugs in the system app directly (or hid them somewhere?!)
tl;dr: I'm trying to obsolete some Date and Time fields from our legacy solution in favor of using DateTime in the extension world. So naturally, I wrote an Upgrade-Codeunit to migrate the data to the new fields just to find out that CreateDateTime() and Time() both act like the session is in the UTC-TimeZone even when I explicitly set the timezone with the SessionSettings-Object to the Timezone the Data got entered in (W. Europe Standard Time)
I don't mind "setting off" the calculated times to get my desired outcome (user sees the time in the "Time"-field represented in the DateTime-Field again - no 2hour shift) But I'm a little lost on how to achieve that goal. - Because i somehow need to find the difference between the local time and UTC to use it for calculation... any Ideas?
I don't want to set the Target to "OnPrem". Otherwise i could use DotNET but or modules are on AppSource and they are really don't like OnPrem there.
My very last option would be to have a function run by the user.. or some webservice trickery. But I would prefer not to overcomplicate and use the tools that where designed for this.
regards
Stefan