This content has been marked as final. Show 8 replies
Just to update you, I have filed bug #13441441 for this issue, 'DYNAMIC ACTION AFFECTED REGION ID NOT PROPERLY CLEARED WHEN IT SHOULD BE'. We have this targeted to be fixed by the first 4.1 patchset.
If this was the case, and to workaround this for the moment without having to edit the export every time, you can go back into the DA, temporarily select 'Region' again for the 'Selection Type', clear the 'Region', change the selection type back to '- Select Type -' again and save this. This should clean this out and get rid of the issue for you.
Hope that helps, let me know if so, or your scenario was different at all. Sorry again about this, but hopefully that workaround is of some use to you and others, until we get this fixed in the patch.
Application Express 4.0.2.00.07
I faced this issue too. It was a dynamic action I had copied from one page to another.
After reading this I removed the offending DA and rebuilt it again from scratch. This worked for me.
IMHO, Ant deserves some points recognition here (hint to Original Poster).
Ran into the problem again today. (We don't have the patch yet :-( )
To find the offending pages I used
SELECT * FROM apex_040100.wwv_flow_page_da_actions da WHERE affected_elements_type = 'REGION' AND NOT EXISTS (SELECT id FROM apex_040100.wwv_flow_page_plugs pp WHERE da.flow_id = pp.flow_id AND da.affected_region_id = pp.id);
We also encountered the same issue and the suggested work around and the query to find out the erratic dynamic actions were very useful to fix it.
Just for easier identification, I have changed the query to return the dynamic action name also.
SELECT de.name, da.*
FROM apex_040100.wwv_flow_page_da_actions da
JOIN apex_040100.wwv_flow_page_da_events de
ON de.id = da.event_id
WHERE affected_elements_type = 'REGION'
AND NOT EXISTS (SELECT id
FROM apex_040100.wwv_flow_page_plugs pp
WHERE da.flow_id = pp.flow_id
AND da.affected_region_id = pp.id);
Thanks to all whoever contributed.