...
In the GoMeddo app, navigate to the Resources tab
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
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? |
|---|
Where?
Type |
|---|
|
| Resource local timezone |
|
| Start/End date & time |
|---|
Date/Time | |
|
|---|
| Current user timezone |
|
|
|---|
| Start/End date & time |
Resource local timezone
Date/Time | |||
| Resource local timezone |
|
|
|---|
Start date
Resource local timezone
Date
Output
| Start/End date | Date |
| Resource local timezone |
|---|
|
Output
|
|
|
Start time
Resource local timezone
Text(5)
Output
| Start/End time |
Output
Local End Datetime
Text(5) | |||
| Resource local timezone |
|
|
|---|
Start date & time
Resource local timezone
Formula(Text)
| 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) | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Page Properties | ||
|---|---|---|
| ||
|
...