Skip to Main Content

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

[APEX 3] Requested source data of the report has been modified

939716May 25 2012 — edited May 25 2012
Hello APEX-Friends,

I have a common problem but the situation is a bit different here. Many of you might know the "invalid set of rows requested the source data of the report has been modified" problem. Often it occurs on submit. That means, you have a report, you select rows, you do things, you submit the page and everything blews up.

This is because you enter some values into fields the report depends on and so you modify your report parameters and the source data changes.

But:

In my case I have a dynamically created report that blews up before any submits occur or values change.

My query is a union of two selects. Both query different views. Those views use a date field as parameter and some compare functions.

I read the field with a V-Function i wrapped arround the apex V Function - declared as deterministic. My date compare function is also declared deterministic (I doubt this makes any differences as it might be only important for the optimizer, but as long as I don't know exactly what APEX evaluates, I go for sure).
I ensured, that the date field is set by default with the current date (and that works, because my interactive report initially displays correct data from the current date).

So everything is deterministic and the query must return same results on subsequent calls, but APEX still throws this "source data has changed" error and I am to 99.99% sure, that this cannot be true.

And now the awesome thing about this:

If I change the value of the date field, an javascript performs a submit. The page is reloaded (without resetting pagination!) and everything works fine. I can leave the page, reenter, do things - everything works well.

But if I log into the application and directly move to the corrupted report and try to use the pagination without editing fields or submitting the page the error occurs.

Do you have any Idea what's happing there? I could try to workaround this by submitting the page the first time it's entered to trigger this "mystery submit" that gets everything working. But I would like to understand this issue and have a clean solution.

Thanks in advance,
Mike aka UniversE
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jun 22 2012
Added on May 25 2012
1 comment
463 views