Hi Scott,
Using getMembers() and a string variable for such high volumes of data is not going to be very effective from a performance perspective and will be limited by length as you've discovered.
The scenario of filtering one BEx Query based on the results of another is best implemented by using Replacement Path Variables of type "Replacement with Query", as described in the following document: Replacement Path Variables - Replacement with Query - They May Save You Some Time
Regards,
Mustafa.
Did you increase the "fetch size" limit as shown in this archived thread? See https://archive.sap.com/discussions/thread/3651038
Hi Tammy,
Thanks for the response. In this case, I don't believe the array fetch size is the issue. I say this because if I remove the string conversion step (the step that allows me to store my array as a global variable), everything runs without incident. At this point, the array has successfully reached 35k records without issue.
The problem seems to be solely the length of the created string. It seems to happen at some length between 10k and 100k characters - my field I'm converting from array to string is 10 characters per row, so this equates to 1,000 -10,000 values.
I'm just wondering if anyone knows how to find this string length limit outside of trial and error and if it can be adjusted anywhere. If not, I can work around the limitation - I had hoped, however, to be able to store some pretty large arrays as global script variables, and I can't do so until SAP potentially adds array global script variables to Design Studio.
Thanks!
Scott
Add comment