Writing / appending to excel

Help
,
1

Scenario:

Trying to add a datatable with ~18 000 cells, consisting of 16 columns and around 1130 rows. Results in “The range does not exist” when trying to do so. I have tried using both append range and write range, but neither work. The four other times I add data to excel (same workflow as issue) work fine. After some testing, I have found that this is dependent on mainly how many columns the data has.

Steps to reproduce:

Did some test runs removing parts of the data with remove column and remove row, which resulted in the following dataset:

Index Rows Columns Total Success?
1 1137 16 18192 no
2 200 12 2400 no
3 200 12 2400 no
4 100 12 1200 no
5 10 12 120 no
6 1000 11 11000 yes
7 500 11 5500 yes
8 250 11 2750 yes
9 220 11 2420 yes
10 200 11 2200 yes
11 10 11 110 yes
12 10 11 110 no
13 1 11 11 no
14 1 10 10 no
15 1 9 9 no
16 1 8 8 no
17 1 6 6 no
18 1 5 5 yes

Index 1-11 is produced by removing the columns from the first part of the dataset, inkluding three rows of dates and times, while 12-18 is by removing the latter part of the columns (mainly short, pure text and one longer description field, usually about 2 sentences.

As you can see, sucess or failure seems to be correlated not to the total amount of cells, but rather the amount of columns, even when using just one row.

Current Behavior:

Expected Behavior:

Studio/Robot/Orchestrator Version:

Last stable behavior: Yesterday, before adding 3 more columns of data to the set
Last stable version: The problem was found while on version 201X.1.63XX (X = cannot remember), before updating to 2017.1.6435
OS Version: Windows 10 Enterprise

1 Like
2

You’re not alone on this, and I am waiting on an update for a fix too. It started happening after one of the Studio updates I believe.

It’s not only dependent on column count, cause rows can cause it too. I recently got the error using 1 column.

You can still use .CSV files, Clipboard, or Text-based data as a workaround.

Let’s hope this is resolved ASAP!

1 Like
3

Hi there,

is this Issue allready fixed in a new Version? I got the same Problem with Uipath Studio and Orchestrator 2018.2.3