Hi all,
Can someone tell me the reason why I am getting the below Attached error: The dataset I have approx 20 lakhs Rows.
Solved! Go to Solution.
Take a look at the field sizes inside your workflow with the select tool. Change the field sizes to apropriate values. If you have report tools inside your workflow, i would do this first right before them.
If you are not sure about which values are apropriate, instead of using the select tool, use the auto field tool. This tool will do the job.
The error that you're seeing relates to the maximum size of data that you can put in a single string. In general there are only 2 ways to get a string that long. Concatenate all your 2M records into a single string or use the table tool to create a single table with all 2M records. This last operation creates what is called a report snippet, which is a representation of the table including all the data and formatting placed into a single field. This can cause a massive increase in the size of the string, due to the formatting information. As example this data concatenated into a string gives a string of length 15.
the same data passed through a table tool creates a snippet of length 1229, the start of which looks like this
<div class="d4b234bf502234f668ab7cd89f162e960" width="100%"><style>
.d4b234bf502234f668ab7cd89f162e960 thead .column0 { numeric:false; }
.d4b234bf502234f668ab7cd89f162e960 .column0 { text-align:right; }
.d4b234bf502234f668ab7cd89f162e960 tbody td { fo..
This an increase of about a 1000 times over the raw data size. Apply this to your entire 2M rows of data and it is easy to see how the snippet can grow to larger than 2GB.
One way to deal with this is to group your data in some way so that instead of getting a single table record produced, you're getting multiples. If you can group your data into 10-100 groups, you'll probably get below the 2GB string limit
Dan
Hai there,
I also get the error "Error: Designer x64: The Designer x64 reported: String size limit reached: Strings are limited to 2147483648 bytes". However it does not state in which Tool the error is. How can U find where the error occurs?