Versions Compared

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

...

Salesforce

...

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)

...

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.

Step-by-step guide

  1. In

...

  1. 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

...

Which timezone?

Label

Field API Name

What

...

?

Type

  • Input & Output on Reservation

...

  • 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

...

Date/Time

  • Input

...

  • in APEX / API / FLOW

  • Output on record page

Current user timezone

  • User Start Datetime

  • User End Datetime

  • B25__Start__c

  • B25__

...

  • End__c

Start/End date & time

...

Date/Time

  • Output on record page

Resource local timezone

  • Local Start Date

  • Local End Date

  • B25__Start_Date__c

...

  • B25__End_Date__c

Start/End date

Date

  • Output on record page

Resource local timezone

...

  • Local Start Time

  • Local

...

  • End Time

  • B25__Local_Start_Time__c

...

...

  • B25__Local_End_Time__c

Start/End time

...

Text(5)

  • Output on record page

Resource local timezone

  • Local Start Datetime

  • Local End Datetime

  • B25__Start_Local_DateTime__c

...

  • B25__End_Local_DateTime__c

Start/End date & time

...

Formula(Text)

...

...

Example

Tip

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

...

Timezones

The calendar displays resources in its own timezone. Even if there are two resources shown in the calendar with different timezones, this will display the reservations in these resources in respect of that resource's timezone. The calendar does not automatically adjust itself based on the user-selected Locale and Timezone.

For Example, if you have two resources, Resource One in (GMT+01:00) Central European Standard Time (Europe/Amsterdam) and Resource Two in (GMT+00:00) Greenwich Mean Time (Europe/London) dragging a reservation with start-time 15:00 from Resource One to Resource Two will result in the local time not being changed, the GMT times will be changed.

Section

The same reservation is shown twice in two resources with different timezones:

Column

Resource One (GMT+01:00)

Image Modified

Column

Resource Two (GMT+00:00)

Image Modified

Related articles

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@101b6
showSpacefalse
sortmodified

...

type

...

page
reversetrue

...

labels

...

time timezone timezones
cqllabel in ( "timezones" , "time" , "timezone" , "date" ) and type = "page" and space = "BPD"

...

Page Properties
hiddentrue

Related issues

Related articles