hard to diagnose without more information on how this "overflow column" is generated. Does it come directly from a table ...? Does a SQL function return the contents ...? It is being concatenated in the SQL itself ...?
It's using a pipeline function, e.g see link below
We have flexible where clauses, and Apex 5.1 didn't allow function returning a query, so we had to resort to SQL query on a pipeline function.
This works fine, but seems to have a 4000 limit on columns at apex 18.1.
I tried the same on apex 18.2 via apex.oracle.com and it works, so maybe a bug at apex 18.1?
1 person found this helpful
hmmm ... possibly this is due to a fixed bug in 18.2 (the fact that it works on apex.oracle.com is an indicator for this). I would need to look into a test case in order to confirm or deny this ...
Here's a shot into the blue: You might try to explicitly convert the column to a CLOB in the SQL query ... maybe that will make it work on your system as well.
That was a good shot in the dark Carsten, did a to_clob on the column and now worked. Thanks for your advice.
Downloaded 18.2 and it didn't resolve the issue, so ended up altering the overflow column on the piped row plsql record type from varchar2 to clob