SAP iRPA Upgrade to Agent 3 Excel Get Values (Cells) Date Format Issue

[alisarde]

Hello,

We have some processes in production, most of them are triggered using Excel templates where users fill in some data, SAP iRPA performs some calculations from that data and enters data into the SAP system.

To work with the dates retrieved from Excel and enter them into the SAP system we have a reusable process that transforms a date in JavaScript Date format to String DD.MM.YYYY format to enter it into the SAP system.

These processes have been in production for some time and they work correctly in all the computers and virtual machines where the processes are executed despite being in different languages (Spanish and English).

We are using the dependencies irpa_core, irpa_outlook and irpa_excel 1.18.97 and the desktop Agent is version 2.0.19.50.

We are starting to migrate to SDK version 1.30.69 to use the Deskop Agent 3 version 3.7.44 and we are facing a problem with the "Get Values (Cells)" activity as we are noticing that it has gone from returning, for cells that are of type "Date", a date in JavaScript format to the String of the cell.

This is causing us problems as in Spanish language computers the Excel date format is DD/MM/YYYY and in English language computers it is MM/DD/YYYY.

We have seen that there is a new parameter in the activity, but it should not influence as they are cells that are always visible.

This is an example of a cell definition in Excel file:

This is an example of Get Values (Cells) activity result in cloud studio debbug mode using irpa_excel 1.18.97 and Desktop Agent version 2.0.19.50 for that cell:

This is an example of Get Values (Cells) activity result in cloud studio debbug mode using irpa_excel 1.30.69 and Desktop Agent version 3.7.44 for that cell:

Is there any way to keep returning the value in JavaScript Date format?

Thank you very much for your help.

[marcin_jakubik · Accepted solution]

Hi Alejandro,

I've entered a ticket for the dev team to take a look at this.

[marcin_jakubik · Accepted solution]

FYI a fix for this behavior should be coming in our 2301 release. Keep an eye out on our What's New. Thanks for reporting!

[alisarde · Accepted solution]

Thank you very much Martin, we are using a workaround depending on the language of the computer where the process is running but we will keep an eye on what you say.

[former_member127886]

new Date("2022-11-01")