What is it?

You can now include timezone offsets when importing date/time properties. Previously, you needed to make sure all of your timestamps were converted to your portal's local timezone before importing.

Why does it matter?

If your team works across multiple time zones, it can be tricky to accurately reflect timestamps when importing data. We currently assume all date time properties reflect the portal's default timezone. Supporting timezone offsets gives power users more control over their data.

How does it work?

When importing to a date time property you can now include a timezone offset to specify the timezone that you're importing to. So for example, -05:00 would be EST, +09:00 would be JST, etc.

When using timezone offsets, you should always format them as follows:

• +HH:MM
• -HH:MM

If a timezone offset is not included, the portal's default timezone will be assumed as before.

Who gets it?

All hubs and tiers