Skip to main content

Dear all

In a customer’s Mobile environment we have found, that datetime fields are no exposed visible on the screen, although they are available on the database. I thought the time zone was picked up by the client itself, but don’t know how to solve this. There has to be a solution obviously, as that error does not appear on different customer’s environment:
 

03/02/2022 06:42:45|ERROR|ConvertDateTimeFromUIToDB|2|EXCEPTION: Argument_TimeZoneNotFound. For more information, visit http://go.microsoft.com/fwlink/?LinkId=623485 ...    at SharedLibrary!<BaseAddress>+0x61e844
   at IFS.FSMW.Architecture.Utilities.MetrixDateTimeHelper.ConvertDateToOppositeTimezone(DateTime dateValue, Boolean isDBToUI)

 

App Params, Client Scripts, Sync Rules have been aligned and match between both environments. Mobile app version is identical too.
 

Job List - Plan Start Dttm is missing
Debrief overview - Plan Start Dttm is missing
DB - Plan Start Dttm available

 

Any hints on how this can be solved?

Please find attached also the full log of the client.

 

Best regards:

Marko

This is most likely a date/time formatting issue.  The display of date/time on the device is dependent on the device settings.  In Windows, this is mostly affected by Preferred language and Regional format.  It may also be possible to make additional, manual settings changes that affect the formatting for date/time.

In general, FSM Mobile supports regional formatting as long as Latin numerals (0,1,2,3,4,5,6,7,8,9) are used by the language.  However, it is certainly possible that some of the hundreds of possible regional formats are not supported.  I recommend trying to change device settings to see if that affects the behavior.

If you identify specific settings where this behavior can be reproduced, it can be reported to Support.  Then a determination will be made if the desired settings can be supported.

Hi @brian.gummin,

This is an issue on Windows platform only, Android works fine with the same environment if that helps.

Prod is same version as Dev, using the same client and device with same timezone/region in Prod works but fails with error in original post. CET is the timezone in use.

Is there anything else that could be prompting this?

Kind regards,

Lee Pinchbeck

Terms & ConditionsCookie settings