This is really needed when working with integrations.Every function that calls Today(), Time(), or are converting between DateTime and Date or Time could end up with very unexpected results!I believe we could add two more options to solve this:4. Add support for a new HTTP Header, called "X-Time-Zone" or similar, that sets the time zone for the web service session. This approach is supported by many other systems.5. Add support for the use of SessionSettings.TimeZone() in a web service session. In that way, we can at least handle the time zone in custom APIs. Actually, the docs (at https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/methods-auto/sessionsettings/sessionsettings-timezone-method) says that this work - but it does not (at least not when I was investigating this earlier)This Yammer thread handles the same request: https://www.yammer.com/dynamicsnavdev/threads/2322620781699072