Hi,
I found an issue with the SQL validation of a classic report in my client's environment, and in an attempt to determine exactly what triggers the issue, I recreated the problem in apex.oracle.com with the following.
Let's say we create a simple classic report region using the following SQL
select dummy, null test1 from dual
where dummy like upper(:P1_CRITERIA||'%')
Where the components might look like this in Page Designer:
If we change the alias test1 to test2, we see the change reflected in the list of columns on the left.
I found in some occasions when I modified the query, I would get the following error in the console, and the columns would not update. This often manifests in the no action being taken when I go to save the page, unless I created another region to trigger a change.
(I had trouble posting this image, so hopefully it comes through... update: it didn't, it's available here)
apmeum.js:88 POST https://apex.oracle.com/pls/apex/wwv_flow.ajax net::ERR_CONNECTION_CLOSED
I narrowed this down to concatenating the '%' to the start of the criteria
select dummy, null test2 from dual
where dummy like upper('%'||:P1_CRITERIA||'%')
I'm yet to eliminate this being some sort of localised network issue, but the fact I could recreate the issue on apex.oracle.com over the dual object was a little concerning.
At one point I also received the following errors
Can anyone reproduce this?