1

Topic: Implementation possibility in IG analog lov and the trigger post-query

Colleagues, hello!
At migration of applications from Oracle Forms in APEX environment (18.1 or 5.1.4) there were difficulties with Interactive Grid and a field defined as lov (or select list). Let we have a unit of the tabular form in Oracle Forms. With the help post-query the trigger and lov it is possible to make so that for some field in the unit all values were deduced, and by means of lov it was possible to select (i.e. to change, add) only some set restricted to a condition. Texts sql quer for lov and for the trigger different, on a condition where. It is necessary in certain cases, to describe long (well for example, the dismissed/moved employee, the data on it should it is deduced for last periods (date), but at adding of new lines it should not be in lov).
In APEX with IG so it is impossible, yes, is lov, but the mechanism similar post-query I I do not see or I do not guess as to implement.
Whether there are at someone ideas on creation of the described mechanism in IG?
Thankful in advance for the help.
p.s.
There is an output to remove grid and to pass on IR + the form. But then users should "spring" often from the report in the form and it is reverse that is not so convenient. Nevertheless, here IG would be much more interesting.
-
Yours faithfully;
rootvg

2

Re: Implementation possibility in IG analog lov and the trigger post-query

rootvg;
We similar solve so:
We write in lov request which to us it is necessary at adding union all select name, id from emp where id = <id the employee current line>
I.e. we add even a line with the current employee. When you look any record where the employee is eliminated to any sign from sampling the second part of a condition fulfills. At us often such requests if record is blocked for usage.

3

Re: Implementation possibility in IG analog lov and the trigger post-query

heavyside wrote:

rootvg;
We similar solve so:
We write in lov request which to us it is necessary at adding union all select name, id from emp where id = <id the employee current line>
I.e. we add even a line with the current employee. When you look any record where the employee is eliminated to any sign from sampling the second part of a condition fulfills. At us often such requests if record is blocked for usage.

The small correction, it is necessary to use union. And if absolutely the user  to do so:

select name, id from emp where id = <id the employee current line>
union all
select name, id from emp where id! = <id the employee current line> and <What that still a condition>

Thus the current line will be always above. smile

4

Re: Implementation possibility in IG analog lov and the trigger post-query

select name, id from emp where id = <id the employee current line> and id! = <ID the user of session>
union all
select name, id from emp where id = <ID the user of session>
union all
select * from (
select name, id from emp where id! = <id the employee current line> and id! = <ID the user of session> and <What that still a condition>
order by 1
);

Here so it is even better smile

5

Re: Implementation possibility in IG analog lov and the trigger post-query

blkangel;
Yes, it is finite union, thought somewhere on road )
With order the good idea, can we use, but somehow never users asked us)

6

Re: Implementation possibility in IG analog lov and the trigger post-query

heavyside, blkangel
Thanks you for the help and for idea! The problem is solved.
-
Yours faithfully;
rootvg