Cascading LOV and submit page

Hi,
I have a series of LOVS on a page each using the 'Select list with submit' attribute and 'Source Used' set to 'Only when current value in session state is null'. The cascade feature works ok once I branch back to the same page. However when I set the 'Select list with submit' attribute on the LOV item I am unable to save the data back to the database with the submit page button.
Any ideas?
Thanks

Steve - Make sure the "save" process fires only when the submit button is used (base the process condition on the value of the REQUEST or use a when button pressed option) and check that no branches are firing before the process runs.
Scott

Similar Messages

Cascading LOV - and order by clause?

Hi, I have a collection that makes use of cascading lovs.
The cascading lov works properly, but I would like the return values sorted alphabetically and cannot figure out why they are not. If I run the query in SQL, it runs perfectly.
My query is:
select......
apex_item.select_list_from_query_xl(15,c015,'select port_name, port
from valid_ports
where state = '
||nvl(c014,0)
*||'order by port_name',*
'style="width:150px;background-color:#FBEC5D;"',
'YES',
'0',
'- Select PORT -',
'f15_' || LPAD (seq_id, 4, '0'),
NULL,
'NO' ) PORT,
c014 is a state code. Order by port_name.
any thoughts? thanks

Hi Varad, thanks for your response. It is the child...here is the full query, it may make more sense.
thanks again!
Karen
{select apex_item.hidden (1,seq_id) checkbox,
apex_item.hidden (2,seq_id)||
        *apex_item.select_list_from_query(3,c003,'select partner_name d, state_code r*
                                                  *from   partners*
                                                  *where state_code is not null*
                                                  *order by partner_name',*
                           *'style="width:100px;background-color:#FBEC5D; "'*
                            *||'onchange="f_set_casc_sel_list_item_port(this,f4_'||LPAD (seq_id, 4,'0')||')"',*
                             *'YES',*
                                *'0',*
                                *'- Select State -',*
                                *'f3_' || LPAD (seq_id,4, '0'),*
                                *NULL,*
                                *'NO'*
                               *) STATE,*
           *apex_item.select_list_from_query_xl(4,c004,'select port_name, port*
                                                    *from   valid_ports*
                                                    *where fips_state = '*
                                                    *||nvl(c003,0)*
                                                    *||' order by port_name',*
                                         *'style="width:150px;background-color:#FBEC5D;"',*
                                         *'YES',*
                                         *'0',*
                                         *'- Select PORT -',*
                                         *'f4_' || LPAD (seq_id, 4, '0'),*
                                         *NULL,*
                                         *'NO' ) PORT,*apex_item.POPUPKEY_FROM_LOV(5,c005,'VESSELS_DE',NULL,NULL,NULL,NULL,NULL,
                                'style="width:150px;background-color:#FBEC5D; "') vessel_id,
      apex_item.text(7,c007,8,null,'style="background-color:#FBEC5D;"'
||'onchange="f_set_start_date(this,f7_'||LPAD(seq_id, 4,'0')||')"') trip_start_date,
        apex_item.text(8,c008,5,null,'style="background-color:#FBEC5D"') trip_start_time,
        apex_item.text(9,c009,null,10,'style="width:100px;background-color:#FBEC5D"') trip_end_date,
        apex_item.text(10,c010,5,null,'style="background-color:#FBEC5D"') trip_end_time,
        apex_item.SELECT_LIST_FROM_LOV(11,c011,'TRIP_TYPE','style="width:100px;background-color:#FBEC5D; "') trip_type,
        apex_item.SELECT_LIST_FROM_LOV(12,c012,'YES_NO','onchange="setMultipleFishermen(#ROWNUM#);"','YES',0,' ','f12_#ROWNUM#') multiple_fishermen,
        apex_item.text(13,c013,3,null,'style="background-color:#FBEC5D"') days_at_sea,
        apex_item.text(14,c014,3,null,'style="background-color:#FBEC5D"') nbr_of_crew,
       -- apex_item.hidden(15,c015) supplier_trip_id,
        apex_item.hidden(16,c016,1) trip_nbr,
        apex_item.text(17,c017,5) partner_vtr
from apex_collections where collection_name = 'TRIP_C'
}

Set Cascading LOV Item using Dynamic Action

Hi all,
I have the following page item:
P1_USERNAME
P1_COMPANY (LOV)
P1_DIVISION (LOV)
P1_DEPT (LOV)
Item P1_COMPANY, P1_DIVISION, and P1_DEPT are cascading LOV on my page.
I also have a table that contains the user and his/her company, division, and department.
So I have a dynamic action that when P1_USERNAME is entered. The dynamic action will pull the COMPANY, DIVISION, and DEPT information from the table and populate the page item accordingly.
I got the dynamic action working, I can confirm this by checking the Session State of the items.
BUT I cannot get the LOVs to display the selected value from the session state. They always reset back to "- Please Select -", which is my display value when NULL.
For example:
I have a record like in the table:
Username :alex
Company : Finance Inc.
Division : Admin
Dept : HR
When I entered the username into P1_USERNAME, this is what I see in the screen.
Username :alex
Company : - Please Select -
Division : - Please Select -
Dept : - Please Select -
While the session states of the items have been set correctly as per the record in the database.
Has anyone experienced this before?
I think it's because the parent LOV (company), reset the child LOVs (division and dept), when the dynamic action kicks in.
Thanks.

I've just taken a look at your sample page and don't think this issue is actually too complicated to solve. (Actually, it was I who was mucking around in page 1, sorry for that. I was looking at it and then had to go. Picked it up again later on and just made a copy this time)
You change the employee. The dynamic action fires, executes plsql and sets the values in the company2/division2/dept2 fields
Company 1 is a cascading lov. Empo has changed? Company refreshes. Cascading for division and dept as well.
You can see this happening in sequence as well when looking at the page. Select emp, it'll hang for a second. You then get the select list refresh icons.
The sequence in which this happens is of course a bit wrong. You set the values for the items on the client side first, but then their refresh is kicked in, and so the value setting is simply lost again.
What makes this annoying is how P1_EMPNO is a cascading lov parent of P1_COMPANY. Changing P1_EMPNO will refresh the lovs beneath it. However, you can't simply set their values after you've retrieved the user's company/division/dept, because each lov is dependent on the one above it. Eg you change the employee. The company lov is refreshed. Because the it is refreshed, the division lov will refresh. Now you can set the value of the company lov, but not that of the division one. Why is this? The lov for division requires the value of company in the session state. If you'd set the value for company after it has finished refreshing, it will already be too late for division to pick up the value set. .
I made a copy of your page to page 5, “tom”.
The first I did was removing the cascade from the company lov. You don’t need this. There are simply no parent lovs for this lov, as is evident from the sql for it. The companies always remain the same companies even when you select another person; it is not dependent on another item for its values.
Then the timing issues come in play, and with them there is also the issue of the session state.
So now companies always show. You pick a user, it runs the PLSQL block and put values in the P5_xxx2 items. P5_COMPANY can be set now, and this is in the set value of the dynamic action. By not suppressing the change event, a refresh will be triggered on its cascading lov, P5_DIVISION.
Refreshing P5_DIVISION will only get the new lov values (constrained within the chosen company) for this item though, and not set the value. We already have the values in P5_DIVISION2 however, and thus can use the “After Refresh” dynamic action on P5_DIVISION to do this. In short: company gets set, divisions refresh to show the correct divisions, and then the selected value is set. Again, by not suppressing the change event on this item the depending lov on DEPT will be refreshed.
Then by using another “After Refresh” dynamic action on P5_DEPT we can set the selected value once more.
Also important is that I changed P5_DIVISION to submit P5_COMPANY when it is refreshed, and P5_DIVISION when P5_DEPT is refreshed. This makes sure that the correct set of values is retrieved and probably why you were struggling aswell. After company has changed and division has refreshed, the value on division is set. But the correct divisions are shown only because the chosen company has been set in the session state.
The same for division - dept. After the refresh of division, the chosen value for division is set. This change will trigger the refresh on dept, and because dept has the division in its page items to submit list, the correct values will be retrieved.
Take note that the “debug items” are required in this solution though. Just set them as hidden and unprotect their value. Your goal should be to reduce the amount of roundtrips to the server. Why do a plsql (ajax) call just to retrieve a session state, when the value is already on the page and all in one action? Three hidden items is just so much easier than 3 extra ajax calls, the tradeoff is plenty.
There is one more noteworthy point, and that is the fact that dept is being retrieved twice. That makes sense because of the cascading lovs. Initially company is changed, and this will refresh division and this in turn will trigger a refresh on dept. At this point the lov for dept will be empty, because division will be empty. Because we set the value of division again after it has refreshed, this will trigger a second refresh on dept, though now the correct list of values is retrieved because division has a value set. Not that big an issue, but good to point out. If you’d have another cascading lov beneath dept, it would refresh three times.

Cascading lovs in Jdeveloper R2

on Jdev R2.
I was doing several different Test with Jdev R2 regarding to cascading Lov and lovs components.
here are results.
lets split them in two flavors.
I. Forms.
a) cascading lovs works fine only if you use : input text item with lovs. (this one works fine even if you do not set autosubmit on the master and partial trigger on dependent lovs, .......cool)
b) if you choose selectOneChoise, "what is really nice for short list" it does not work. not even if you set autosubmit and partial trigger.
II. af:table
a) on editing mode: editAll
* using input text with lov works (you do not need to set autosubmit/partial triggers) but every time when you select a value from a list, an ugly error araise saying : field1 is required. field2 is required...to all require attributes (you can work after click)
* using selectOneChoise did not work. after you select the first lov the next lov is surrounded by red square and never get refreshed.
b) on editing mode: clickToEdit :
this is really cool and fast, but cascading lovs does not work at all. not even input text with lovs
has anybody any feedback/workaround/idea on this one, or should we wait until these bug get fixed, hopefully in the new release.
also I was wondering what is the best approuch to execute some java code on load/unload.?
thank you for any help.
Luis

to call java on load use af:clientlistener along with af:serverlistener.. use the type as load
http://blogs.oracle.com/jdevotnharvest/entry/how-to_call_server_side_java_from_javascript
or use the beforephase and afterphase property of f:view, refer navaneeth code here
popup on page load using managed bean, using jdev-11.4
use af:document's onunload property for unloading event and java calls

Cascading LOV in BEx Query OLAP Universe + BEx variable

Hi gurus,
we have an universe where a Cascading LOV has been defined based on a BO Hierarchy ( based on a BW hierarchy), the OLAP universe is based on a BEx query.
Now, when the users create a WebI report selecting a value from the value list, the Cascading LOV appears and the user selects the value, descending by the nodes.
We are analyzing the universe performance and we are testing to add some time BEx variables in the query ( in the current version no variables are used).
Everything works properly but when we try to select a value from the Cascading LOV and try to select a lower level the webI returns a mdx error indicanting that the time variable is not informed. (WIS 10901: A database error ocurred; MDX query can not be executed: specify a value for the variable Z... )
We thought that the mdx for the LOV get values from the MD table because in the infoobject definition, it has the Business Explorer Settings:
Query Def. Filter Value Selection = Value in Master Data Table
Query Execution Filter Val. Selectn = Value in Master Data Table
The Query Execution Filter Val. Selectn can be defined at the infoprovider also (with the provider specific Properties of the infoobject) and also at the query, whe have not modify none of them.
My first question is which settings has efect at OLAP Universes, the infoobject settings; the infocube settings or the query settings ?
Are the Cascading LOV integrated with BEx Query OLAP Universe?
Is it an application error?
Many Thanks in advanced.
Best Regards,
Nuria

Hi Ingo,
many thanks for your quick answer.
That was one of the possibilities we have analized but the problem is that the user has to inform the hierarchy level for all the reports, that kind of variables is translated in the universe as a prompt
Now we have only one universe and some business analists users create reports themselves for the business area based on that universe.
The users create WebI filters without prompts,just filtering the hierarchy node. If we add the BEx variable then the user sould inform the prompt for all the reports based on that universe.
We want to avoid that prompt, we have several hierarchies in the query for different infoobjects.
Thanks again.
Best Regards,
Nuria

Cascading LOV bug??

Hi all...
please help with this issue.
Not sure whether it is a bug or browser issue.
APEX: 4.1
Browser: IE 7
Database: 11g
If i have a cascading lov, and if i have a some javascript
under the HTML FORM ELEMENT ATTRIBUTES ""onchange="alert('hi');"""
The on-change event is firing twice.
why is it firing onchange twice?
please check the following app.
http://apex.oracle.com/pls/apex/f?p=41803:2
select a dept, you will get 2 alert messages.
Is there any fix for this?

Hi Earl...
Thanks for the reply.
Yup..as you said , it seems it a browser issue (IE 7).
Instead of using the onchange javascript .. i moved my javascript code to "dynamic action". It works fine now.
Thanks for the reply.

Need help in completing Denes Kubicek code: cascading lov in tabular form

Hi, I have been working off of Denes Kubicek demo for cascading lovs and have finally (!) gotten it working....sort of.
Denes's instructions indicate that you must request an account in order to receive the code. I have done so, but have not had a response....can anyone help me on what needs to be done in oder to complete his instructions?
thanks!!
here is his helpful code:
http://htmldb.oracle.com/pls/otn/f?p=31517:176:2537143614094776

sorry. my query is now:
select
apex_item.hidden(11,seq_id) seq,
apex_item.hidden (12,seq_id)||
apex_item.select_list_from_query_XL(13,c013,'select distinct s.common_name d, s.species_itis r
from species s, species_qc c
where partner_id = '||:f200_issuing_agency||' and
c.species_itis = s.species_itis order by s.common_name',
'style="width:220px" '
|| 'onchange="f_set_casc_sel_list_item(this,'
|| 'f16_'
|| LPAD (seq_id, 4, '0')
|| ')"',
'YES',
'0',
'- Select Species -',
'f13_' || LPAD (seq_id,4, '0'),
NULL,
'NO'
) SPECIES_ITIS,
apex_item.select_list_from_query(14,c014,'select disposition_desc d, disposition_code r
from dispositions
where displayed = 1 order by disposition_desc') DISPOSITION_CODE,
apex_item.text(15,c015) reported_quantity,
apex_item.select_list_from_query(16,c016,'SELECT DISTINCT unit_desc ,unit_of_measure
FROM species_Qc s, units_of_measure u
WHERE s.unit_of_measure = u.unit_measure
AND species_itis = '||c013||'AND partner_id = '||:F200_ISSUING_AGENCY,
'style="width:220px"',
'YES',
'0',
'- Select Unit -',
'f13_' || LPAD (seq_id, 4, '0'),
NULL,
'NO' ) UNIT_MEASURE,
apex_item.SELECT_LIST_FROM_LOV(17,c017,'SALE_DISPOSITION') SALE_DISPOSITION_FLAG,
apex_item.text(18,c018) PRICE,
apex_item.text(19,c019) PERMIT_ID,
apex_item.select_list_from_query(20,c020,'select market_desc d, market_code r
FROM market_categories
where market_code in (select distinct market_code
from species_qc
where species_itis = '||c013||'
and partner_id = '||:F200_ISSUING_AGENCY||')',
'style="width:220px"',
'YES',
'0',
'- Select Market -',
'f13_' || LPAD (seq_id, 4, '0'),
NULL,
'NO' ) MARKET_CODE,
apex_item.text(21,c021) GRADE_CODE,
apex_item.text(22,c022) trip_id
from apex_collections c
where collection_name = 'CATCH_C' and
c.c022 = :F200_CURRENT_TRIP_ID
UNION ALL
select
apex_item.hidden(11,null) seq,
apex_item.hidden (12,null)||
apex_item.select_list_from_query_XL(13,0,'select distinct s.common_name d, s.species_itis r
from species s, species_qc c
where partner_id = '||:f200_issuing_agency||' and
c.species_itis = s.species_itis order by s.common_name',
'style="width:220px" '
|| 'onchange="f_set_casc_sel_list_item(this,'
|| 'f16_'
|| LPAD (9900 + LEVEL, 4, '0')
|| ')"',
'YES',
'0',
'- Select Species -',
'f13_' || LPAD (9900 + LEVEL,4, '0'),
NULL,
'NO'
) SPECIES_ITIS,
apex_item.select_list_from_query(14,null,'select disposition_desc d, disposition_code r
from dispositions
where displayed = 1 order by disposition_desc') DISPOSITION_CODE,
apex_item.text(15,null) reported_quantity,
apex_item.select_list_from_query(16,null,'SELECT DISTINCT unit_desc ,unit_of_measure
FROM species_Qc s, units_of_measure u
WHERE s.unit_of_measure = u.unit_measure
AND species_itis = '||0||'AND partner_id = '||:F200_ISSUING_AGENCY,
'style="width:220px"',
'YES',
'0',
'- Select Unit -',
'f13_' || LPAD (9900 + LEVEL, 4, '0'),
NULL,
'NO' ) UNIT_MEASURE,
apex_item.SELECT_LIST_FROM_LOV(17,null,'SALE_DISPOSITION') SALE_DISPOSITION_FLAG,
apex_item.text(18,null) PRICE,
apex_item.text(19,null) PERMIT_ID,
apex_item.select_list_from_query(20,null,'select market_desc d, market_code r
FROM market_categories
where market_code in (select distinct market_code
from species_qc
where species_itis = '||0||'
and partner_id = '||:F200_ISSUING_AGENCY||')',
'style="width:220px"',
'YES',
'0',
'- Select Market -',
'f13_' || LPAD (9900 + LEVEL, 4, '0'),
NULL,
'NO' ) MARKET_CODE,
apex_item.text(21,null) GRADE_CODE,
apex_item.text(22,null) trip_id
FROM DUAL
WHERE :request = 'ADD'
CONNECT BY LEVEL = 2
I have two issues:
1. the item tab_cascading_item is not populated when the value of c013 (species) is changed.
2. I receive an error when trying to add a row to the collection. My code for doing so is:
begin
for i in 1..1 LOOP
apex_collection.add_member (p_collection_name => 'CATCH_C',
p_c013 => null,
p_c014 => null,
p_c015 => null,
p_c016 => null,
p_c017 => null,
p_c018 => null,
p_c019 => null,
p_c020 => null,
p_c021 => null,
p_c022 => :F200_CURRENT_TRIP_ID );
end loop;
end;
I am so close on getting this....any help would be appreciated.

Cascading LOV submit

Hi.
I have a FORM that create or update table record.
In this form i have create a LOV (regions).
After we have another LOV (province).
I want that when i select my region, the "province lov" will be populated only with appropriate province.
Now i have setted region LOV as a Selected list WITH SUBMIT, but when i try to choose my region, the form will be submitted :( and i don't want that!
How can i do???
Thanks.
Edited by: 890410 on 18-ott-2011 7.36

Hi 890410,
In your "*LOV (regions)*" make sure you have the:
Page Action when Value Changed --> None (default)
In your "*LOV (province)*" make sure that the:
Cascading LOV Parent Item(s) --> LOV (regions) page item.
and that the:
Optimize Refresh --> Yes
This was the child LOV will be populated with the correct data set once the application user has selected a Region.
daniel
Edited by: zooid on 18-Oct-2011 11:23

Apex 4.2.1 - mobile theme display bugs and Cascading LOV bug

I've setup a test at http://apex.oracle.com/pls/apex/f?p=35331 - username/password is test/test
Simple page to show some issues I'm running into. Wondering if work-arounds exist or if a patch would be available before we'd go live.
First and second issue are the same I believe. So - a normal text box (label1) looks fine. But, Label2 is a Display only item and Label3 is a read-only select list item. As you can see - both of the values appear smack dab right beside the label and not in line with the other fields. It's totally ugly and not usable as is. I've tried to move this over, but the label goes with it. I can see no way of doing it, but wondering if there's some hack I can put in to solve it...
The last issues is with a cascading LOV. Simple table setup. Static on the first, the second a simple query that filters on the first. If you set the select list to Value Required and not to display null values - then when you click on the Second List button - it just hangs. The page is unusable. I suspect this has to do with the null or something. But - doesn't appear to matter if anything is chosen. Note - if the list is large - which I think then uses a different UI control, this is fine. Only when one of the lists is small does the issue reproduce.
Any workarounds or fixes? Any ideas?
Thanks

Hi,
I would suggest to not mix different questions and a thread for each of them. Makes it easier for others to follow.
About your problem with the cascading LOVs, it appears that this is/was a bug in jQuery Mobile which we use under the hood. I was able to reproduce the problem with APEX 4.2.1 using jQM 1.2.0, but was not able to reproduce it with APEX 5.0 which will use jQM 1.3.0RC1 or higher. The problem occurs if a select list is empty.
There are different workarounds available:
1) set the attribute "HTML Form Element Attributes" of P1_CLOV_2 to data-native-menu="false"or
2) set the attribute "Display Null Value" of P1_CLOV_2 to Yes and "Null Display Value" to - select - (or something similar). The "Value Required" = Yes will still guarantee that a value has to be picked. Having the extra null entry will guarantee that the select list always contains an entry, that seems to workaround the bug in jQuery Mobile.
I have filed bug 16355963 - jquery mobile: empty select list causes javascript error
to track that this is definitely fixed in APEX 5.0.
Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Cascading LOV not working when the page is public

Hi ,
I have a cascading LOV in a tabular form which I have built using Denes Kubicek example from
http://apex.oracle.com/pls/otn/f?p=31517:176:2702932664861989:::::
Thanks to this wonderful examle I was able to make my cascading lov work.
However when I make the page public , the second lov(which is based on the first one) does not work.
Inorder to debug i changed get.get('XML') to get.get() and put an alert on it; to check if the select list string is being returned correctly by the application process - it returns null. The same alert returns the select list string when I put the authentication back on the page.
Also I noticed when the page is public the application item (TAB_CASCADING_ITEM) is not getting populated with the value of the first select list.
has anybody encountered the same issue ?
Appreciate any suggestions?
Thanks,
Dippy

One of the parameters in the htmldb_get is the page the process runs on. You should change that to the current page or make page 0 public as well.

Default value in LOV field in Create and Update page in OAF

Hi All,
I am unable to default LOV field in Create and Update page in OAF.
I tried in below way :
OAMessageLovInputBean lovBean1 = (OAMessageLovInputBean)webBean.findChildRecursive("AAA");
But I am getting developer mode exception, so please guide me how i can set the default value for create and update page instead of using code in process request method in controller.
Thanks

Hi,
1) In case of create, you can default the value either in EOImpl or in AM while initializing the row:
//in EOImpl
public void create(AttributeList attributeList)
super.create(attributeList);
setXXAttribute(<value>);
//in AM, VO new row initialization :-
VOImpl VO = getVO1();
VO.setMaxFetchSize(0);
VORowImpl row = (VORowImpl)VO.createRow();
row.setXXAttribute(<value>);
VO.insertRow(row);
row.setNewRowState(Row.STATUS_INITIALIZED);
2) In case of update, execute the VO (also set the where clause if required) in PR method of update page.
--Sushant

ADF LOV and Cascading LOV in JDeveloper 11.1.1.5.0 Issue

Hi,
I have created business component ExpenseHdrView and added LOV and Cascaded LOV. If I run the application module I could see the LOV is working. It is displaying list of values and Return value(id value is not dispalyed as expected). But when I include the view in an ADF form then LOV is working but in the form when I select any value it is displaying the corresponding ID value. This is not in sync with business component.
I am new to this ADF world. Am I doing anything wrong or missing something?
Please help.
Thanks,
Mehabub

Hi Kalpesh,
I just tried, and didn't get that error - there must be something specific to your scenario. Have you tried the obvious solutions (reinstall)
John

Cascading LOVs (v4) and retaining the child value

I've implemented the default delivered implementation in version 4 (4.0.2.00.07 to be exact) of cascading LOVs. Working fine except for one thing...after refresh of a child LOV, the previously selected value is wiped out even when it's still a valid value in the child LOV. If it's an invalid value, I can understand that it would be wiped out, but if it's still valid, I'd like it to be retained.
Example...let's say I have these two select-lists (parent and child).
P100_PARENT
P100_CHILD
P100 Child's SQL references P100_PARENT:
where b.child = NVL(a.parent,b.child)
Optimize refresh is also set to 'No' because I need the child to refresh to all children selections when parent is null.
In short, the parent is optional. If Parent is null, show all child options regardless of Parent. If Parent is defined, show only the child options for the parent.
So when parent is null, I get all child options (OK). I pick one.
If I go to parent and change it to a specific value that IS the parent of the child I chose, my expectation is the child select list should refresh (it does) but if my chosen value is still in the list, it should scroll to it and select it. Instead, it wipes it out.
To put some values into the example...
Let's say parent values are:
A
B
C
null
Let's say child values are numbers such that valid values are:
1 through 10 when parent is A
11 through 20 when parent is B
20 through 30 when parent is C
1 through 30 (any child value) when parent is null.
So I have a null parent LOV value and the child shows me 1 through 30 (OK). I pick 15.
I change the parent to 'B'. Child list refreshes (OK). But while 15 is still a valid value in the list, it is not selected again (my value is wiped out). I still want it to have '15' selected.
Any workaround? Is this a bug? Enhancement opportunity?

Hi Matt,
have you had a look at Skill Builders "Save Value on Cascade" dynamic action plug-in? See http://skillbuilders.com/oracle-apex/Application-Express-APEX-Consulting-Training.cfm?tab=free-plugin-downloads
Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Is there a way you can make a contact page with blank fields to put info. on iWeb and submit it to my email?

is there a way you can make a contact page with blank fields to put info. on iWeb and submit it to my email?

It depends on where you publish.
MobileMe users need to use a form service or MailShoot...
http://www.iwebformusicians.com/Website-Email-Marketing/Form-Service.html
http://www.iwebformusicians.com/Website-Email-Marketing/MailShoot.html
If you publish to another server that supports php you can do it yourself...
http://www.iwebformusicians.com/Website-Email-Marketing/Contact-Form.html
"I may receive some form of compensation, financial or otherwise, from my recommendation or link."

How to prevent apex 4.0 shuttle cleared by cascading LOV setting?

I have a shuttle control for choosing a list of database users populated from a child table by an On Load - After Header process, which then repopulates the child table in an On Submit - After Computations and Validations process. Work fine.
I then set the shuttle's Cascading LOV Parent Item(s) to a text item that could be used for filtering the shuttle's LOV, and revised the LOV SQL to a) use the filter and b) include items stored in the child table, i.e.:
select username as dv, username as rv
from all_users
where username like upper(:P5_USERSFILTER) || '%'
union
select username, username
from user_grouping_users
where groupid = :P5_GROUPID
order by 1
Unfortunately, when the filter value changes (P5_USERSFILTER), the state of shuttle (as set in my On Load - After Header process) is cleared. The values from the child table are properly included in the LOV, but they are no longer selected -- so the appear in the left-hand list as candidate values but not in the right-hand list as selected values. Additionally, any items selected in the shuttle before changing the value of the LOV Parent (:P5_USERSFILTER) are no longer selected.
Is there a way to prevent the selections of a Cascading LOV item from being cleared when the parent item is reset?
Note, I've specified 'No' for Optimize Refresh, and 'P5_USERS' for Page Items to Submit and 'Yes' for Display Extra Values (which in general does not seem to have any affect on a shuttle LOV)

Hallo all!
I got a similar situation: a text item that filters the left side of an shuttle item (P11_IAG_ENUM), but the right side should stay the same - independet from the text item, where search-phrases are entered.
So I tired with your example - thanks for that - but I changed the code that I only have one collection 'P11_IAG_VALUES' ... but right side seems to be still dependend from the search item. I also deleted the "set value" action of the "save current selection"-dynamic-action, because I supposed it's not needed.
Here is my "save current selection"-dynamic-action:
DECLARE
c_collection CONSTANT VARCHAR2(30) := 'P11_IAG_VALUES';
l_seq_id NUMBER;
BEGIN
IF NOT apex_collection.collection_exists(c_collection) THEN
apex_collection.create_collection(c_collection);
END IF;
SELECT MIN(seq_id)
INTO l_seq_id
FROM apex_collections
WHERE collection_name = c_collection
IF l_seq_id IS NULL THEN
apex_collection.add_member (
p_collection_name => c_collection,
p_c001 => :P11_IAG_ENUM );
ELSE
apex_collection.update_member (
p_collection_name => c_collection,
p_seq => l_seq_id,
p_c001 => :P11_IAG_ENUM );
END IF;
COMMIT;
END;
... and the "restore old selection"-dynamic-action:
DECLARE
l_selected_iag VARCHAR2(32767);
BEGIN
SELECT c001
INTO l_selected_iag
FROM apex_collections
WHERE collection_name='P11_IAG_VALUES'
RETURN l_selected_iag;
EXCEPTION
WHEN NO_DATA_FOUND THEN
RETURN NULL;
END;
Where is my error in reasoning?
(Meanwhile I try to create an example application...)
[Edit: I got problems to acces my workspace, try to reset my password --> error, even try to find my workspace -->error .... everytime the same; I'll try it later again, but hoping that anyone can help me without example application]
Edited by: kc7 on 10.09.2010 09:20
[Edit II: I finally created a example-application: *http://apex.oracle.com/pls/apex/f?p=30216*
workspace: kc7
user: dummy
pwd: doll
Edited by: kc7 on 10.09.2010 12:28

Cascading LOV and submit page

Similar Messages

Maybe you are looking for