Hi, we had the same error, the same error message like the one you mention and it appeared on that part in our script where we used MapSubstring() function.
We resolved the problem by ensuring the mapping table has all the values that the function MapSubstring is going to encounter when applied. If we load, e.g. partial load with the first 10 records only and our mapping table has more rows, the problem appears. If we don't filter anything and the source mapping table contains all values, then there is no problem.
I have exactly this problem.
can you please explain me what exactly should I correct?
what values do I have to add to the mapping table?
I opened a discussion on the subject, yesterday
I will be happy if you could take a look.
I desperately needed this model.
the title of the discussion :
place: App Development.
Thanks a lot.
The "out of object memory" script error introduced in 2.6 has been fixed in the 2.7 update.