Skip to Main Content
Feature Request FR-3360
Product Area Page Components
Status CLOSED

1 Voters

"error during rendering of region" error message unclear (calculated field dividing by 0)

derik.tran Public · Sep 13 2023

Idea Summary
Can we have Interactive reports/grids automatically handle the DIV/0 calculated field issues rather than throwing out a generic error “error during rendering of region”?

Use Case
Users create calculated field and it's working until the denominator sometimes become 0.  If the user doesn't address it in the formula using a DECODE statement, the page gives them a generic error "error during rendering of region".  It doesn't say which field is causing it and so forth.  

Preferred Solution (Optional)
The preferred solution would be to automatically render the value to 0 if that's the error so the users don't have to worry about it.  Otherwise, we need to capture and report that error much better to at least point out the column(s) generating the error vs a generic error as the above.

We reviewed this idea carefully, and while it was interesting, we concluded that due to all the internal implications we need to take into account, it is not feasible in APEX.

Comments

Comments

  • carsten.czarski APEX Team OP 1.7 years ago

    Hmmm … Interactive Grid as well as Interactive Report get their data by executing a SQL Query. When computed columns come into the picture, these are executed by adding the computation expression to the SQL query; at the end, one(!) SQL query is generated, which executes all of the report, including all filters, computations, aggregates and more. This ability to have the database executing everything as a SQL query is the key feature of APEX components.

    And now we’re in the area of SQL execution: whenever an expression in a SQL query divides by zero, the database (!) raises ORA-1476 - divisor is equal to zero.

    So, I’m afraid this idea is infeasible, because of the SQL centric nature of Interactive Grids or Interactive Reports. The only way to implement that idea would be APEX executing all computations and filters procedurally, without SQL. But that would have huge performance impact, especially on larger data sets.

    So, all in all I’m afraid there is no way to get around the ORA-1476 - divisor is equal to zero error …

    Regards

    Carsten