Versions Compared

Version Old Version 29 New Version Current
Changes made by

Luuk Koetsier (Unlicensed)

Jerome Vincendon

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

You may have resources in different timezones, this article explains how to deal with those.

Info

Configuration in Salesforce Classic

In order to keep configuration simple, please perform the following steps in Salesforce Classic (GoMeddo is Lightning-Ready, you may afterwards use the app in Salesforce Lightning as you please)

Info

Salesforce always renders Date and DateTime fields relative to the timezone of the user that is viewing them. This means GoMeddo needs some specific fields to allow for correctly inputting and outputting reservation dates and times.

...

  1. In the GoMeddo app, navigate to the Resources tab

  2. In the Resource hierarchy, make sure that every timezone's top node (defining the timezone of itself and its children) has the correct timezone filled in in the Timezone field. Its children will automatically be given the same timezone

  3. Now strictly follow the following matrix for inputting and outputting reservation dates and times in either the reservation's resource's timezone or the viewing user's timezone:

Input / Output

Fields

Which timezone?

Label

Field API Name

What

?Where

?

Type

  • Input & Output on Reservation

form and findAvailableDimensionIds

  • Form

  • Input in APEX / API / FLOW

Resource local timezone

  • Start (local time)

  • End (local time)

  • B25__StartLocal__c

  • B25__EndLocal__c

Start/End date & time

Resource local timezone

Date/Time

  • Input

on Reservation form and findAvailableDimensionIdsEnd (local time)

  • in APEX / API / FLOW

  • Output on record page

Current user timezone

  • User Start Datetime

  • User End Datetime

  • B25__Start__c

  • B25__

EndLocal

  • End__c

Start/End date & time

Resource local timezone

Output

Local End Date

Date/Time

  • Output on record page

Resource local timezone

  • Local Start Date

  • Local End Date

  • B25__Start_Date__c

Start date

Resource local timezone

Date

  • B25__End_Date__c

Start/End date

Date

  • Output on record page

Resource local timezone

Date

  • Local Start Time

Output

  • Local

Start time

  • End Time

  • B25__Local_Start_Time__c

Start time

Output

Local End time

Resource local timezone

Text(5)

  • B25__Local_End_Time__c

Start/End time

Resource local timezone

Output

Local End Datetime

Text(5)

  • Output on record page

Resource local timezone

  • Local Start Datetime

  • Local End Datetime

  • B25__Start_Local_DateTime__c

Start date & time

Resource local timezone

Formula(Text)

  • B25__End_Local_DateTime__c

Start/End date & time

Resource local timezone

Formula(Text)

Output / Input through API or Process

User Start Datetime

B25__Start__c

Start date & time

Viewing user timezone

Date/Time

Output / Input through API or Process

User End Datetime

B25__End__c

End date & time

Viewing user timezone

Date/Time

Example

Tip

The following screenshots display a real-world example based on a resource in London (GMT) and a user in Amsterdam (GMT+1)

...

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@101b6
showSpacefalse
sortmodified
showSpacetypefalsepage
reversetrue
typelabelspagetime timezone timezones
cqllabel in ( "timezones" , "time" , "timezone" , "date" ) and type = "page" and space = "BPD"labelstime timezone timezones

Page Properties
hiddentrue

Related issues

...