Af:query component with cascading Lov's

Hi All,
I have Cascading LOV's model setup in Business Components and they work fine in a form or table
but they are not working inside af:query component as there is no autoSubmit attribute on the query component itself
can someone help me to resolve this
Thanks in Advance

I have found a way
using bindings attribute of the query component it was able to go to backing bean on any LOV change in there we need to manually refresh the bindings then it works

Similar Messages

New Blog Post: Saving Current Values with Cascading LOVs

All,
Just blogged on Saving Current Values with Cascading LOVs: http://bit.ly/hQPUPi
Enjoy!
Regards,
Dan

Monty,
Glad to hear it's working for you.
Oh, you just had to go there ;) Popup LOVs are a bit more difficult because the values are not automatically brought back to the page for you. I've already worked out how this could be implemented in my head - but writing it up, of course, is more of an effort. I've added it to my list of blog articles to write on. Since it's not a requirement right now, I'll cover another topic first and come back to that one afterward.
Regards,
Dan
Blog: http://DanielMcGhan.us/
Work: http://SkillBuilders.com/apex/

Resetting a Form with Cascading LOVs (Apex 4)

A standard reset button cannot reset cascading LOVs properly. Let's assume we have a parent LOV and a child LOV. When one changes the selection in the child LOV, reset can undo this. But when he changes the selection in the parent LOV, reset will undo only the parent LOV but not the child LOV. The child LOV remains unchanged (however the selection is lost) and therefore shows a list that does not correspond to the entry now shown in the parent LOV.
Has anybody found a solution for this, a reset action that can reset cascading LOVs completely and properly?
Regards
Roland

Roland,
i didn't try this myself but maybe you succeed with triggering the onchange-event of your parent-select-list (this should cause the child select-list to be refreshed).
Or you could try if a form region has a apex "refresh" event (i know that refresh works on reports).
brgds,
Peter
Blog: http://www.oracle-and-apex.com
ApexLib: http://apexlib.oracleapex.info
BuilderPlugin: http://builderplugin.oracleapex.info
Work: http://www.click-click.at

Is it possible to use the af:query component with programmatic VOs?

My understanding is that the view criteria in a normal SQL-based VO are used to add WHERE clauses to the VO.
Since programmatic VOs do no have this capability, is there something I need to override in the view object implementation class to support the view criteria that will be established by the af:query component?
Does someone have an example of how this might be done?
Thanks, -Klaus

Unfortunately no. The remote control will work, but the radio will not.
The radio only works with the iPod video and the nano.

Dynamic Change event getting error with cascading LOV's

Hi all,
In my application (v4.0.0), I have two sets of cascading drop-down select lists, these each make up a date (year, month, day) plus a time value (not cascading).
I also have a dynamic action that gets the hours difference between the two dates set above. This fires on the change event.
When I change, say the month drop-down, the day list is refreshed. But before it is refreshed, it looks to be emptied and the change event fires. I then get an error from the dynamic action because the day value passed to the query is empty (confirmed when looking at POST data).
Can anyone think of a workaround idea for this? e.g. a way to set the dynamic action to conditional?
Thanks!

Hi Peter
Thanks for the tip, I have tried this and it has helped, although not solved the problem. I was originally getting two errors appear ("AJAX call returned server error ORA-01843: not a valid month for Set Value.") and this has removed one of them...
When looking in Firebug, it seems to me that although the dynamic actions (cascading update + set value) are running one before the other, the values aren't updated in order. e.g. the cascading update is not applied before the set value action is run.
Could this be a bug with dynamic actions?

Multiple queries happeing in adf query component using LOV

Hi,
I am using a programmatic view object in adf query component and have created List of values for one attribute by adding another programmatic ViewObject as ViewAccessor.
To populate the lov ViewObject, i have overwritten the method executeQueryForCollection in which i call the webservice to fetch the data. So lov is working fine inside QueryComponent.
I have overwritten queryListener attribute of query component in my backing bean. In the queryListener method, to populate the result grid, am populating the view object by using createRow and insertRow apis. While doing so, Whenever i do setAttibute for the lov field, the overwrittern method executeQueryForCollection getting invoked. Hence my webService getting invoked. So if i have 10 rows, the webservice is getting invoked 10 times.
I put sops in the executeQueryForCollection method for the queryMode and getName.
System.out.println("executeQueryForCollection::::"+this.getQueryMode()); i get as 7
System.out.println("executeQueryForCollection:::=" +this.getName()); i get as CurrencySummaryLOVVO_5708_findByVC_ The number 5708 varies for every row.
Please tell me How to avoid invoking the executeQueryForCollection everytime when i do setAttribute.
One workaround i have currently is to have one dummry attribute for the lov which can be used for display in grid and actual attribute will be used in Query Component for the lov to function.
Is there any other better workaround?
Thanks a lot in Advance.
Vivek
Edited by: Vivek Singh on Oct 22, 2009 9:16 PM

When you set a value to LOV field it tries to validate it from the LOV data. thats why it execute query.
Try setting Row Level Bind Values = false for the accessor.
yet, i would suggest to find an other way to populate values of LOV since the executeQueryForCollection will be executed many times when you use that LOV:
[http://adfbugs.blogspot.com/2009/08/lov-execute-query-many-times.html]

'is null' not working in dynamic sql and SQl Query component (OBPM 10gr3)

I'm using a SQL Query component with sql like this
'select col1, col2 from table where col3 is null'
for some reason this does not work.
Has anybody faced this issue? Is there a known bug with handling nulls
Thanks

plz post which DB version u r working with
dont use paramters in Procedure with : sign
Write simply the name of the Paramters like p_userid etc etc
this might help u as well
http://baigsorcl.blogspot.com/2010/02/get-rid-of-addtional-quotes-with-quote.html

Session State Protection breaks Cascading LOV.

Hi,
Whenever I turn Session State Protection on my application , with option 'Arguments Must Have Checksum' on the page level,
Items defined with a cascading LOV will not work. Once session state protection is on for the page, and I change the value of a parent
LOV, the Child Item LOV (defined with Cascading LOV) will not show any value and the 'round working icon' will just keep on going
and does not end, The Child/Cascading LOV seems to be just hanging and not return any values. This happens consistently (APEX 4.1.1.).
There are no threads existing for this behavior, would like to know if this is a known issue and if there is a fix.
Thanks,
Ramon

The documentation says, "If you need to set this item's value in session state using Ajax, then an Unrestricted protection level must be used for the item (for example in Dynamic Actions, Set Value, Page Items to Submit or Cascading LOVs, Page Items to Submit)." In practice, what this means (among other things) is that items that are identified as "Cascading LOV Parent Item(s)" must have "Session State Protection" set to "Unrestricted".

Query Component - Flexible Conjunction

I have a requirement to query data using Query component with the flexibility for the conjunction to be used. For example,
If I have 3 fields to query (note that in advance mode, rather either using All or Any (AND and OR), I would like to provide the flexibility to allow user to determine which conjunction to use:
A = x OR B = y AND C = z
or
(A = x OR B = y) AND C = z
Thanks.

Please state the version of JDeveloper you're using when posting to this forum. I'll assume JDev 11g.
The af:query component does not support what you're looking for. In your case you'll need to build something out of the more basic components yourself.
CM.

af:query component - need help

hi
I am implemeting a search page wiht <af:query> component with view criteria. (to be specific drag and drop viewCriteria as query panel with table)
what i observe is that when I do "Add fields" at runtime the compnent moves up and up till it hides the panelHeader and the other fields with no access to it.
After i refresh the screen the component comes back to its normal positon but pushes the table component below it down till its barely visible.
This component seems to be very unstable.
Let me know if there is any workaround without making the screen unstable.

Hi,
You can find some related info here..
Can I achive valueChangeListener in af:query?
and
http://jobinesh.blogspot.com/2011/03/retrieving-viewcriteria-from-custom.html
Thanks,
TK

Query component using toplink.

Hi,
I am trying to implement query component with toplink entity. Please provide any document or sample application related to this.
Thanks in advance.
Vamsi

Have you tried a simple search (http://www.oracle.com/pls/as111210/search?word=toplink) which get you http://docs.oracle.com/cd/E24382_01/user.1112/e17455/dev_toplink.htm#OJDUG1094
Timo

Problem with cascading dependent LOV query running when it should not

I have a page fragment with a regular ADF form on it that I use to add new entries to a table. This form has many fields on it with LOV’s associated with them. I have dependent LOV’s on some of them. The one case I have is I have three fields A, B, and C. Field C is dependent on A and B. The problem I seem to be having is when I enter a value for field A using it’s LOV, I get an hourglass for a long time after I select it and before it is displayed on the form. If I delete field C from the form the problem goes away. If I change the query behind the view for the LOV for field C to include a rownum < 20 in the where clause the problem goes away. My question is, why would the selection of a value for field A cause the query to fire for field C’s LOV view and how can I stop it. I don’t really want to use the rownum in the where clause.

i had lot of question?
The problem I seem to be having is when I enter a value for field A using it’s LOV, I get an hourglass for a long time
ok. are using? any complex query to pick the lov 'a' .
Answer: The LOV for A is based on a read only non-EO view with a SQL that is not really very complex. The LOV definition does set multiple values when the selection is made to blank out dependent fields in the data model used by the main form.
after I select it and before it is displayed on the form.
here i cant undestud?
Answer. The order of things is I open the main form, I click the mag glass to open the LOV popup, I select the row I want and click the OK button. Navigation returns to the main form where I get the hourglass waiting for the selected value to be displayed in the field on the main form.
If I delete field C from the form the problem goes away. If I change the query behind the view for the LOV for field C to include a rownum < 20 in the where clause the problem goes away.
ok.
why are you going to delete the value of c?. At intial stage you can make empty after selecting a and/or b you can load into c.
Answer: I physically deleted field C from the main form to see if that was what was causing the long delay. When I run the main form without field C I do not get the hourglass. That is how I know they are related.
My question is, why would the selection of a value for field A cause the query to fire for field C’s LOV view and how can I stop it.
you may set partial trigger to c depends for 'a'.
or else lov 'c' query depends on 'a'
Answer. The query for C's LOV does depend on the value returned when I select a value for A. They are cascading LOV's. Will setting the partial trigger stop the SQL for field C from running? Is the SQL running because I'm blanking out field C when I change the value for field A?
am not sure i understud correctly. can you pictuarize you problem with an example.

Cascading LOV always returns first row in af:query

HI
JDEV 11.1.1.3.0
A strange thing is happening with my cascading LOV which is input text with LOV.
I have a read only table with a query section. I then also bring up any of the tables rows in a popup with single record view where the row is then in an af:form for inserting and updating.
Both the af:query and af:form have the cascaing LOV in them.
When testing the cascading LOV in the BC Browser it works fine. When I use it in the popup in the af:form record it works fine. But in the af:query section, no matter which row I choose in the LOV, it always returns the 1st row of the LOV back to my input text component.
Has anyone experienced this...any ideas?
Thanks,
Mario

Aha...and the above log message lead me to the solution!! :-)
The VO is based on an Oracle data dictionary view, DBA_TAB_COLUMNS. When you create the read only VO, by default it does not create any of the attributes as "key" attributes, because the oracle view has no primary key.
Setting owner, tableName and columnName as key attributes solved this issue, now my cascading LOV works in the BC Tester, af:query component and my af:form component.
Regards,
Mario

Setting default value read from user session, for an LOV in Query component

I want to set the default value of a field in VO that participates in a named view criteria and thereby in Query component. That field is configured with an LOV by mean of a view accessor. The values are Y and N and the corresponding display strings obtained from view accessor are true and false respectively.
I am able to set the default value by setting the value of the criteria item corresponding to that field in view criteria. I am setting the value as either Y or N and I am able to corresponding display string as per the view accessor, on the query component when it is rendered.
I want to read the defauilt value from the ADF BC user session and set it as default value. I tried setting the values as "adf.userSession.userData.usageFlag". Iam ensuring that the attribute usageFlag is set before the view activity that has the query component is invoked. But this is ending up showing no default value in the Query component when rendered.
Can any one let me know how to go about with this?

I made up your table since you didn't provide some example, but I'm sure this will give you the picture:
SQL> var run_type varchar2(1)
SQL> exec :run_type := 'A'
PL/SQL procedure successfully completed.
SQL> create table my_cycles as select level cycle_id
2                            ,      level cycle_status
3                            from   dual connect by level <= 5;
Table created.
SQL> select cycle_id
2 from   my_cycles
3 where case
4           when :run_type = 'D' and cycle_status = 1 then 1
5           when :run_type != 'D' and cycle_status in ( 2, 3 ) then 1
6         end = 1;
CYCLE_ID
         2
         3
2 rows selected.
SQL> exec :run_type := 'D';
PL/SQL procedure successfully completed.
SQL> /
CYCLE_ID
         1
1 row selected.
SQL>

Failing to refresh LOV fields added in the query panel with table

Hi.. Iam using Jdev 11.1.1.2.0
I have a scenario like ..i need to add 2 cascaded lovs in search panel and clicking on search button, the result should be displayed in table form.
For example..
I have cascaded LOV fields departmentId and Firstname ,
first name dropdown values depends on the selection of value in DepartmentIddropdown. I need to add only these 2 fields in search panel and clciking on search buton , the result should be displayed in emp table.
I have achieved the same creating View criteria with 2 fields and dragging and dropping that as query panel with table. But my problem is First name lov is not populating based on department id. It is showing static dropdown list.
Please help me how to achieve this ? thanks in advance.
Regards
Alekhya.

Thanks for the reply.. actually if iam using those cascaded lovs in a form then we can set properties as u mentioned to refresh and display values correctly in the dropdown.
My scenario is like i need to use those fields in query panel header
code snippet
<af:panelHeader text="Employees" id="ph1">
<af:query id="qryId1" headerText="Search" disclosed="true"
value="#{bindings.EmployeesViewCriteria1Query1.queryDescriptor}"
model="#{bindings.EmployeesViewCriteria1Query1.queryModel}"
queryListener="#{bindings.EmployeesViewCriteria1Query1.processQuery}"
queryOperationListener="#{bindings.EmployeesViewCriteria1Query1.processQueryOperation}"
resultComponentId="::resId1"/>
</af:panelHeader>
Iam not having any field names to add properties.
Regards
Alekhya

Af:query component with cascading Lov's

Similar Messages

Maybe you are looking for