Timestamp change - Verify the default timezone for {{timestamp}} in imports

Integrator.io
, ,
1

Hi,

I've been reading about Celigo's upcoming change to the timestamp helper (defaulting to UTC if not specified) and I'm curious about something: Why are only HTTP request body and Relative URI affected by this timezone change and why aren't mappings, filenames, or other areas using timestamp affected?

Is there a technical reason behind this selective implementation? I'd love to understand the logic and whether there are plans to extend this to other parts of the platform in the future.

And a second question: the article does not specify from which user profile the timezone will be picked. This is important because multiple users could have different timezones set, and it's unclear which one will be used. Could you clarify this?

2

@nuriensing this is only affecting HTTP request body and Relative URI because they are the only places in the platform that don't already have the desired behavior.

As for which user timezone, those 2 fields are currently using the account owner's set timezone if no timezone is set in the handlebar. After this fix, it will not use any user timezone (and already hasn't been everywhere else in the platform).

3

Thanks @tylerlamparter