Apex version 188.8.131.52. I am editing an existing classic report which has the column heading option set to 'PL/SQL function returning a colon delimited list of headings'. I have been looking for some time but I cannot find where this PL/SQL function is defined. Can any one point me to the right direction? I do not see anything in the documentation either.
When this option is selected, then there should be a text area shown right underneath the radio group with the label "Function returning colon delimited headings: (Value Required)". In that text area you should see that function - if one is defined, or enter your own PL/SQL function.
Thanks for the quick reply. That is where I thought it would be but unfortunately I do not see any text box with that heading at all. Right after the radio buttons, the column listing starts. I do not see this option any where on the page. Not sure what is going on.
I created a brand new report and I can see the text box for pl/sql function if I select that option for the column heading. For some reason, it is not showing up for the existing report. The report has over 100 columns so I am wondering if the HTML is not being rendered correctly.
It turns out that APEX does not display the text box for the column heading function if there is a lot of columns in the query. It appears to be a bug. I tried I.E, Firefox and Chrome but all had the same problem. To fix this, I had to do the following::
- In 'Region Definition' tab, change 'Maximum number of generic report columns:' to 10. It was initially set to 200.
- Go to 'Reports Attribute' tab and the text box now appears for the column heading.
- Edit the function and change back 'Maximum number of generic report columns:' to the original value.
Hopefully this can help some one who has stumbled across this issue.
I would certainly agree with Tony that 60 or 100 columns are a bit much. But there should be some indication why something is not working, even if it's only a message stating that there's only a certain number of columns supported. So I'll log a bug to improve this in APEX 5.0.