cancel
Showing results for 
Search instead for 
Did you mean: 

Where does Blue Prism inherit its internal date format from?

foehl
Level 6
I have 4 VMs set up in a server/runtime resource config; 2 machines for a test environment and 2 for a production environment. One of the machines (the test runtime resource) is handling dates natively in Blue Prism as MM/dd/yyyy while all other machines use dd/MM/yyyy.

As an example, if I perform AddDays( 01/03/2020, 1) on 3 of the machines, the result is 02/03/2020 as expected, but on this one machine I get 01/04/2020. If I use the date picker in the Evaluate Expression window to pick the 1st of March 2020 on that machine the field is filled with 03/01/2020.

Similarly, a process run on production or directly on the test server gives the expected date while running the same process on the runtime resource results in an incorrect date.

The regional settings of the machine are set to dd/MM/yyyy and all other regional settings match the production runtime VM, but the problem persists.

Does anyone know in detail what the relationship is between the format Blue Prism uses for dates and the settings of the machine it's running on, or what might be causing my issue?

------------------------------
Felix Oehl
------------------------------
1 BEST ANSWER

Helpful Answers

John__Carter
Staff
Staff
Hi Felix, these may help:

https://portal.blueprism.com/documents/v6-data-sheet-date-and-time-handling
http://portal.blueprism.com/customer-support/support-center#/path/1465504592

------------------------------
John Carter
Professional Services
Blue Prism
------------------------------

View answer in original post

4 REPLIES 4

John__Carter
Staff
Staff
Hi Felix, these may help:

https://portal.blueprism.com/documents/v6-data-sheet-date-and-time-handling
http://portal.blueprism.com/customer-support/support-center#/path/1465504592

------------------------------
John Carter
Professional Services
Blue Prism
------------------------------

The support center article gave me the solution, it was the local value in the local user settings file.

Thanks for the quick response John, much appreciated!

------------------------------
Felix Oehl
------------------------------

Hi John,

So the support center article indeed gave us a solution, but it seems to only solve the problem when the process is running in debug mode. Once we run the process from control room, the dates are again handled in MM/dd/yyyy format.

Is there some other Blue Prism setting that makes a distinction between running the process manually (so in debug mode) and running it from control room or could there be something else causing this issue?


------------------------------
Jordy Van den Brande
------------------------------

I don't think so Jordy, the Session Logs section in the guide says: Session logs are stored in the database in the local time of the resource which ran the session, along with an offset value which describes how the time zone of the resource relates to UTC. Session log times are displayed in the user interface as the local time on the resource when the session ran. 

If you contact our support team they may be able to help you check the settings across your environment - DB, app server, resource machines, client machines, locales, config etc, to check everything is aligned.

------------------------------
John Carter
Professional Services
Blue Prism
------------------------------