I thought setting up a faux-APEX session might have done the trick, but alas.
Are you just trying to test your SQL? Because I'm not sure there really is an issue, per se.
ie - this query belongs in the context of APEX.
Thanks for the reply.
No, we have multiple apex_item queries which we are executing on SQL developer to check/validate the output.
No - what? Still sounds like testing?
Other usage of apex_item may work fine, because they're just string manipulation - but this query relies on LOV defined in shared components for an application, hence the tighter coupling.
In my application, apex_item query is used in multiple pages so to check the output and changes we need to run this query in SQL developer.
The same code is working fine with 4.2 so why its creating issue in 5.1?
how can we handle apex_item query in 5.1, do we have any other option to use?
1 person found this helpful
outside of an APEX environment, you need to run APEX_UTIL.SET_WORKSPACE or APEX_UTIL.SET_SECURITY_GROUP_ID before calling APEX_ITEM functions.