Hi everyone,
I’m facing an issue related to excel numeric values vs. displayed values when working with UiPath, and I’d like to ask for best practices.
In my excel file, some cells contain numeric values like;
actual value(in formula bar): 2194915.253871
displayed in the cell: 2,194,915
this difference happens because the cell is formatted with 0 decimal places so excel visually rounds the number however the underlyling value is still decimal.
If I enable use display format in read range what happens if the cell is not fully visible and appears as #### due to column width?
will UiPath read ## or will it still read the underlying numeric value.
has anyone faced a similiar issue before?(excel displayed value vs actual value mismatch)
Use Excel activity Read Range activity.
1 Like
If you are using modern excel process scope, you have the option to select raw value, default and so on.. in use excel file.. you can choose it from option..
If you are using classic , simply use read range excel activity
3 Likes
Thanks for your help
1 Like
If this design helped you fix the problem, please mark as solution so it can help others too 
1 Like
Hi @ayse.cecen
If “Use Display Format” is enabled, UiPath reads exactly what’s visible—including #### if the column is too narrow. So it will read ####, not the actual number.
To avoid this, either don’t use display format or make sure columns are wide enough before reading.
1 Like
Instead of using the classic activity, I proceeded using the modern activity. I didn’t select a display format; I read the Excel file using Excel Process Scope, Use Excel File, and Read Range, and created a new datatable. I then imported this datatable into a new Excel sheet, thus obtaining the desired format without any corruption.
1 Like
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.