Skip to main content

Why af:autoSuggestBehavior fails for input component with immediate=true ?

Sharing a point that I learned today. Thanks to my colleague Srinathreddy(who owns LOV) for this tip. Quoting him:
The af:autoSuggestBehavior tag will not work as you are expecting when it is used with input component whose immediate property is set to true. When immedaite is set to true on the editable input components, the validation happens during the Apply Request Values phase and this is the same phase in which the autoSuggest event is also processed. If there is a validation failure (there is good chance for validation failure here because mostly user enters only a partial text expecting an 'auto suggest' ) the autoSuggest popup will not be shown.


Vinitha said…
This comment has been removed by the author.
Vinitha said…
Nice tip jobinesh.. Can you please help me with a sample of yours wherein the autoSuggestBehavior property usage can be well understood...
Amaan Junaid said…
In my case immediate is set to false.
But then also, autosuggest behaviour is not working fine.
The autosuggest popup comes up, and goes out with an invalid error message.
Please help. Wat can be possible cause.
ajaxaa said…

I just creating ADF component programmatically inputtext, RichInputComboboxListOfValues etc, so I want to add AutoSuggest programmatically created input,RichInputComboboxListOfValues components.

I think below class make it.
AutoSuggestBehaviorTag suggest=new AutoSuggestBehaviorTag();

suggest.setParent(Tag); // The AutoSuggest is where is include

How to Tag class implement with Inputtext component.
There is an alternate approach I implemented on autoSuggest – you can try that as well:

Autosuggest Behavior in ADF

Popular posts from this blog

Happy New Year 2018 !

We can't go back and change the beginning, but we always can start where we are and change the ending. Believe in yourself and you will be unstoppable!

Wishing you and your family a very happy new year 2018 !!!

How to set Bind Variable Values at runtime ?

In this post I'm sharing a couple of approaches for programmatically setting bind variables values at run time. This post is an attempt to explain 'When to use what ?'[ In case if you are familiar with 'Bind Variables' in ADF BC, please refer Section 5.10, Working with Bind Variables in Fusion Developer's Guide ]

1. Set the Bind Variable value using RowSet::setNamedWhereClauseParam(...)

You can use use the setNamedWhereClauseParam(...) method on the ViewObject interface (which extends oracle.jbo.RowSet) to set the value for bind variables. Please note this sets the value on default RowSet. In other words, this doesn't have any effect on the secondary RowSets that you/system generates.
ViewObject vo = am.findViewObject("EmployeesView1"); vo.setNamedWhereClauseParam("bindVarDeptId", new Number(10)); vo.executeQuery();
2. Set the Bind Variable value using ViewObject's VariableValueManager::setVariableValue(...)

VariableValueManager Ma…