Skip to main content
Question

Timezone queries

  • September 30, 2026
  • 0 replies
  • 20 views
Do Gooder (Customer)

Hi, fairly new to IFS and I’m working on helping with a cloud upgrade that’s going to be global as opposed to UK only, and some of our testers have queries about dates and time zoning.

 

I’ve done a little testing on my own of course - with default companies and the global one (uk based) in each region with a before and after midnight time for Australia and USA and it looks like global and Australia local times set the ates correctly, but stay correct to local in other regions.  that raised a few questions I am unable to answer - Could you help?

 

Thanks for looking into this for us.   I am not 100% clear on how you've done your tests, but our concern primarily focuses on four issues identified so far:

 

  1. Some date/time fields in IFS Cloud seem to display a time zone annotation after the field on the screen, and some do not.  We have seen examples on the one screen, where two date/time fields show different time zones.   This led us to question how date/time fields behave in terms of date/time.  Technically, this probably boils down to:

    1. How the data is stored (one might assume it's always stored as GMT, but that might not be the case).

      I know Default storage setting is GMT

 

    1. How the data is displayed (which time zone is used to calculate the displayed value (and is this the same for all fields in the system)

          Time zone can be set from browser and from the time zone toggle in the user settings, I know, but not sure how this interacts or is calculated

 

    1. What drives that display (Time Zone configured for the user's IFS Profile, Browser Regional Settings, Computer Regional Settings etc).

          Time zone can be set from browser and from the time zone toggle in the user settings - but do the different settings affect things differently in IFS.

 

 

    1. How are durations calculated that might use more than one date/time field.

 

we’ve noticed where it shows GMT/BST etc based on date, but that it can confuse users when the clocks change between transactions start and finish 

 

  1. When data is migrated into the system from external sources (and typically this just has dates with no times), what is the behaviour?  Noting that all our APAC/NA data migrations are extracted from our systems with local dates, provided for Data Migration (occurring in the UK).

     

 

 

  1. When data is manually entered into the system during use, which time zone is going to be used for storage and which for display.

    we THINK it Should default to GMT but aren’t 100%

 

  1. How is the Date Display format controlled (CoPilot research on this for IFS seems to indicate that this might vary module to module)

     

 

The resulting concern is how do we provide our users across the Globe with clarity around dates and times in IFS.   We have noted that for all our testing here in APAC, that most dates seem to display in the US date format (MM/DD/YYYY) rather than the GB or AU norm of DD/MM/YYYY.

 

can you help?

Terms & ConditionsAccessibility statement