Good morning experts,
while implementing a script, I have found that the dateToMilliseconds function returns a different data depending on the language selected by the agent. In the image you can see the difference between a date in Spanish language, versus English, so it implies a different result of this function. :

Is there any workarround we can use? thanks

Spanish:

English:

Good morning experts,
while implementing a script, I have found that the dateToMilliseconds function returns a different data depending on the language selected by the agent. In the image you can see the difference between a date in Spanish language, versus English, so it implies a different result of this function. :

Is there any workarround we can use? thanks

Spanish:

English:

It looks to me to be more about locale then language. Assuming you are referring to the Date portion specifically, remember in the US dates are written with month and day reversed when compared to the rest of the world (and, may I add, any sensible approach! - Let's start an indignant flame war 😜) i.e. in the US the format is mm/dd/yyyy but elsewhere it's dd/mm/yyyy. 

So, for example, in the US today (18th July 2024) would be written 7/18/24 in the US and 18/7/24 in the rest of the civilized world.

Looking at your examples, it would appear that this is what is happening.

HTH

Good morning experts,
while implementing a script, I have found that the dateToMilliseconds function returns a different data depending on the language selected by the agent. In the image you can see the difference between a date in Spanish language, versus English, so it implies a different result of this function. :

Is there any workarround we can use? thanks

Spanish:

English:

Hi Paul, 

I could reproduce the scenario, just changing my default laguage into genesys cloud UI....As you thought, anyone should be able to change their language into the UI, and this should not affect on how Scripting is implemented...so my approach arround this is that this should be corrected in GC side....

It looks to me to be more about locale then language. Assuming you are referring to the Date portion specifically, remember in the US dates are written with month and day reversed when compared to the rest of the world (and, may I add, any sensible approach! - Let's start an indignant flame war 😜) i.e. in the US the format is mm/dd/yyyy but elsewhere it's dd/mm/yyyy. 

So, for example, in the US today (18th July 2024) would be written 7/18/24 in the US and 18/7/24 in the rest of the civilized world.

Looking at your examples, it would appear that this is what is happening.

HTH

Good morning experts,
while implementing a script, I have found that the dateToMilliseconds function returns a different data depending on the language selected by the agent. In the image you can see the difference between a date in Spanish language, versus English, so it implies a different result of this function. :

Is there any workarround we can use? thanks

Spanish:

English:

David,

Heh, you won't get any argument from me on that one! I was just trying to offer a perspective on what exactly appears to be happening and possibly why.

Now, as to how to deal with it, and whose responsibility that is.... 🤷‍♂️

Hi Paul, 

I could reproduce the scenario, just changing my default laguage into genesys cloud UI....As you thought, anyone should be able to change their language into the UI, and this should not affect on how Scripting is implemented...so my approach arround this is that this should be corrected in GC side....

It looks to me to be more about locale then language. Assuming you are referring to the Date portion specifically, remember in the US dates are written with month and day reversed when compared to the rest of the world (and, may I add, any sensible approach! - Let's start an indignant flame war 😜) i.e. in the US the format is mm/dd/yyyy but elsewhere it's dd/mm/yyyy. 

So, for example, in the US today (18th July 2024) would be written 7/18/24 in the US and 18/7/24 in the rest of the civilized world.

Looking at your examples, it would appear that this is what is happening.

HTH

Good morning experts,
while implementing a script, I have found that the dateToMilliseconds function returns a different data depending on the language selected by the agent. In the image you can see the difference between a date in Spanish language, versus English, so it implies a different result of this function. :

Is there any workarround we can use? thanks

Spanish:

English:

Thank you very much Paul, for the help, but it's really frustrating when things like this happen, and having to handle this kind of scenarios within the script itself, as we haven't found any other way to solve it :)

David,

Heh, you won't get any argument from me on that one! I was just trying to offer a perspective on what exactly appears to be happening and possibly why.

Now, as to how to deal with it, and whose responsibility that is.... 🤷‍♂️

Hi Paul, 

I could reproduce the scenario, just changing my default laguage into genesys cloud UI....As you thought, anyone should be able to change their language into the UI, and this should not affect on how Scripting is implemented...so my approach arround this is that this should be corrected in GC side....

It looks to me to be more about locale then language. Assuming you are referring to the Date portion specifically, remember in the US dates are written with month and day reversed when compared to the rest of the world (and, may I add, any sensible approach! - Let's start an indignant flame war 😜) i.e. in the US the format is mm/dd/yyyy but elsewhere it's dd/mm/yyyy. 

So, for example, in the US today (18th July 2024) would be written 7/18/24 in the US and 18/7/24 in the rest of the civilized world.

Looking at your examples, it would appear that this is what is happening.

HTH

Good morning experts,
while implementing a script, I have found that the dateToMilliseconds function returns a different data depending on the language selected by the agent. In the image you can see the difference between a date in Spanish language, versus English, so it implies a different result of this function. :

Is there any workarround we can use? thanks

Spanish:

English: