As I understand the way how the grid builds its DML statements it's by design that Automatic Row Processing is not working. But according to the online help manual processing with Target Type set to PL/SQL Code or even Table should work. So I guess you are facing a bug. I suppose you have two processes of Automatic Row Processing type on your page - "Save Interactive Grid Data" and "Save Interactive Grid Data_1" and the first one disabled by Server-Side Condition=Never. But seems that APEX engine ignores that condition and still try to use the process (have a look at LEVEL9 debug). So the work around is to delete "Save Interactive Grid Data" process.
you were right. I did have two processes in this demo seems like error was coming from automatic row process using region source that triggered even it was set to Never.
I drop it now and manual PL/SQL seems to be running fine.
Thank you for bringing this up. Appreciate your help.
Marko Goricki suggested yesterday that setting column of aggregate fnc to HTML expression makes Automatic Row processing working without errors. I have to check this. But it exposes a column that we might not want to show.
Again both are workarounds for something we all believe should be working out of the box. Right!?
P.S. Marko's suggestion did not work. HTML Expression still throws the same error when on Auto process using region source.
LinoS you got me wrong. Not HTML expression, but SQL Expression. Change column source to the SQL Expression and as a source use row_number() over (order by EMPNO desc), as in my tweet: https://twitter.com/mgoricki/status/1097803938286444545
I was just about to change my reply
For the reference I updated my demo to show both. Marko's example works too. Thank you both.
Still all think there is a bug feature of IG in there.