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