Cascaded LOV issue

Hi,
I have a cascaded LOVs. Ideally it should work like this.
Select a value from the first combo box LOV and based on the value selected, populate the second LOV and so on.
When first LOV changes, in the second LOV, the first element should get selected by default. However this is not happening. Instead user is forced to choose an option from the LOV manually.
Any help in how to select the first element in the LOV automatically?
Regards,
Raghu

Hi,
The solution shouldn't be that complicate. Just create a valueChangeListener in your first LOV's component.
You need to update your model in the valueChangeEvent with your new value of yourFirstLOV:
    public void countryChanged(ValueChangeEvent valueChangeEvent) {
        ADFUtils.setValueToEL("#{bindings.yourFirstLOV.inputValue}",valueChangeEvent.getNewValue());
        ADFUtils.setValueToEL("#{bindings.yourSecondLOV.inputValue}",0);
   The value for LOV are actually the indexes on the list of the element.
If you are no using ADFUtils here is the implementation of that method:
    public static void setValueToEL(String el, Object val) {
        FacesContext facesContext = FacesContext.getCurrentInstance();
        ELContext elContext = facesContext.getELContext();
        ExpressionFactory expressionFactory =   facesContext.getApplication().getExpressionFactory();
        ValueExpression exp = expressionFactory.createValueExpression(elContext, el, Object.class);
        exp.setValue(elContext, val);
    }   Try this and post your results. Then only bad thing I can see from this is that if your name's bindings ever change (for example, change from yourSecondLOV to yourSecondLOV2) then you will have to update the java code.
Regards
Sorry, I had to edit because I made a mistake, now you should be able to try and post your results
Edited by: Alejandro T. Lanz on Mar 4, 2013 8:41 AM

Similar Messages

  • 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

  • Cascade LOV in Apex 4.0

    Hello Apex Fun
    how can i make cascade list of value in Apex 4.0 ? i tried cascade which enabled in list of item properties but contain problems , please help me
    also when use that cascade the Arabic characters shown unclear ..
    Edited by: Moh Loay on Aug 24, 2010 2:46 PM

    Hi Moh Loay,
    I think you have to help me with that one, because I tried to reproduce that on apex.oracle.com and was not able to.
    1) I have created page http://apex.oracle.com/pls/apex/f?p=47158:22 which is a cascading LOV on the tables DEPARTMENTS and EMPLOYEES.
    2) For Department "Construction" I modified some of the employees to contain arabic and chinese characters
    3) I executed above page
    4) Changed the department to "Construction" which refreshed the employees select list
    5) Opened the Employees select list and everything shows up as I have entered it.
    Can you please verify with the above page that it looks good for you as well. Maybe it's an operating system/browser issue?
    If the above test case works for you, can you please create a test case with your failing data on apex.oracle.com so that I can have a look what's actually wrong. After you have done that, please provide the workspace, user and password so that I can access your application.
    Thanks
    Patrick
    My Blog: http://www.inside-oracle-apex.com
    APEX 4.0 Plug-Ins: http://apex.oracle.com/plugins

  • 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

  • 4.2.1 Bug: Current values of child cascading LOVs are LOST.

    Hello, ApEx Team!
    This bug affected 4.1.1 and 4.2.1 but with different behavior. It seems that someone was trying to fix it.
    According to docs "whats new in 4.1" a value of refreshed child cascading lov is derived from default value settings of select list.
    Please follow these steps to see the bug.l builder-work done for you here http://apex.oracle.com/pls/apex/f?p=14110:1
    1.Create primary select list P1_SEL1.
      Display null value: Yes
      LOV definition:
        select 'aaa' name,'a' id
          from dual
         union all
        select 'bbb' name,'b' id
          from dual
         union all
        select 'ccc' name,'c' id
          from dual2.Create child select list P1_SEL2.
      Cascading LOV Parent Item: P1_SEL1
      Page Items to Submit: P1_SEL2 (I strongly believe that this item should be submitted automatically along with Parent Item)
      Display Null Value: Yes
      LOV definition:
        select 'aaa' name,'a' id
          from dual
         union all
        select 'bbb' name,'b' id
          from dual
         where :P1_SEL1 in ('b','c')
         union all
        select 'ccc' name,'c' id
          from dual
         where :P1_SEL1 in ('c')
      Default: return :P1_SEL2;
      Default Value Type: PL/SQL Function Body3.Run app. and manually change P1_SEL1 and P1_SEL2 to 'bbb'.
    4.Manually change P1_SEL1 to 'ccc'.
    h2.
    In apex 4.1.1..
    you see that P1_SEL2 is resetted to NULL automatically. The value of P1_SEL2 is LOST. Although I tell apex to submit P1_SEl2 value to set its session state, but the session state still remains NULL.
    The session state of P1_SEL2 is always NULL and I have no idea how to set it as it is set in a browser at the moment of changing parent LOV P1_SEL1.
    h2.
    Now apex 4.2.1.
    It seems this bug is fixed. Indeed it is NOT fixed.
    To see this bug in 4.2.1 just...
    5.Create a third child select list P1_SEL3 which depends on P1_SEL2.
      Cascading LOV Parent Item: P1_SEL2
      Page Items to Submit: P1_SEL3 (Again, I hope you will always submit current item automatically as you do for the parent item)
      Display Null Value: Yes
      LOV definition:
        select 'aaa' name,'a' id
          from dual
         union all
        select 'bbb' name,'b' id
          from dual
         where :P1_SEL2 in ('b','c')
         union all
        select 'ccc' name,'c' id
          from dual
         where :P1_SEL2 in ('c')
        Default: return :P1_SEL3;
        Default Value Type: PL/SQL Function Body6.Run app. again. Manually set P1_SEL1, P1_SEL2 and P1_SEL3 to 'bbb'.
    7.Change P1_SEL1 to 'ccc' and see the bug:
    1) P1_SEL2 is reset to NULL for just a short time and than restored to 'bbb'.
    2) P2_SEL3 is reset to NULL. So the session state was NULL for this item at the moment of calculating default value. As a result the value of child cascading lov is LOST.
    So this bug is still present in 4.2.1.
    Can I hope to get workaround for this problem in 4.1 and 4.2?
    Thank you,
    Vladimir
    Edited by: vgoncharov on 17.12.2012 19:37
    Edited by: vgoncharov on 17.12.2012 22:45

    Good to hear this is already being worked on.
    When we tried to work around the "Automatic detection" bug - changing the "Application Language Derived From" to "Application Preference" or "Session" - we hit issue that some page processes were not firing in translated application.
    See Page processes not firing in Translated applications
    Jan

  • 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

  • Are cascading LOVs possible in af:query?

    Is it possible to have two or more cascading LOVs in an af:query area based on a view criteria?
    I'm having some trouble with dependant (child) LOVs: they filter correctly but return nothing to the field from which were launched.
    I can attach a code snippet if necessary
    Thanks
    JDeveloper 11.1.1.3.0 with ADF BC
    Anybody has ever tried it?
    Edited by: Marge on 02-sep-2010 23:17

    Is it possible to have two or more cascading LOVs in an af:query area based on a view criteria?Yes, it is possible
    There might be something wrong in the configuration, Can you upload the sample app so that it will be easy to figure out the issue.
    Sireesha

  • 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.

  • 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".

  • 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.

  • Cascaded LOV do not work in derived universe

    Hi all,
    Can ay body help me on this.
    Cascaded LOV do not work in derived universe. The same cascaded LOV works                                                          
    well in component / core universe. 
    For Example:
    say object state is generated as Cascaded LOV's with city. in core universe. when you create a webi report based on the core uiverse and drag the object state it Cascaded LOV's are generated.
    now say you create aother universe as derived with the same universe as core universe. Now create a webi report based on derived universe try to drag the state object the cascaded LOV's do not get displayed.
    Note:we have not included any object of the core in the derived universe.
    Any help would be appreciated.
    Thanks,
    Florencio.

    Hi Joe,
    Thank you for your reply. Actually this is not a migrated derived universed. Yes it is the case with migrated reports from R2 to R3.1 till FP 1.3. But it is resoved in Fixpack 1.4 and above.
    In addition it is also a issue in Plain R3.1 with even sample universes that is e-fashion. it is resolved in FP 1.4.
    Thanks Again!!!!
    Florencio.

  • Cascaded LOV loose value when pooling disabled

    Hi All,
    I am using jdev 11.1.1.5
    my scenario is i have search VO with transient attributes.Most of attribute are LOV using accessor.
    Few of LOV are dependent on each other. When i am running by enabling pooling true.it is working fine.
    But when pooling disabled, cascaded LOV are not persisting value in the VO. It is happening only for dependent LOVs . I am not sure  why is it so.?
    I am creating a new row of Search VO usng Create Method of VO operation.Should i try anything else?
    Is anyone faces this issue earlier?  any suggestion to handle this. All attribute are passivated and VO have key attribute.
    Please suggest?

    Hi Frank,
    Well all LOV are transient attribute.Problem is this - Everything working with AMPooling enbaled.But when AMPool disabled then only attribute whose value are depend on other LOV are not persist or loose.
    Yes they are marked passivate. and i also override afterRollback and beforeRollback in all ViewObjectImpl.java with commenting super call.
    Seems , variable are setting by bind variable are not passivated the value. I am not sure, is it some strange behavior or i am doing anything wrong.
    What you suggest  to investigate further more on this?
    Regards
    Vinay

  • Problems with  4.1.1.00.23 Cascading LOVs

    I have a pages with 4 levels of cascading LOVs. These are:
    MEMBER_ID => ACCOUNT => COMMODITY => EXPIRY
    The issue I am running into is that these work fine up through the first three and then fails (or rather simply doesn't do anything) on EXPIRY. I have no idea what or what to do to get this last level to populate. I have confirmed, using the values present in the session that the query for EXPIRY should return data.
    The top level is a simply Select List Control using a Named LOV with this query:
    select
    case organization_type
      when 'Member' then NAME || Chr(32) || LEGAL_NAME
      when 'Bank' then LEGAL_NAME
    end d,
    ID r
    from mbrdata.ORGANIZATION
    order by name, legal_nameThe next level, ACCOUNT, is set up as a cascading LOV. The parent is the MEMBER_ID.
    Named LOV     
    Display Extra Values     
    Display Null Value     
    Cascading LOV Parent Item(s)     P15_MEMBERID
    Page Items to Submit     
    Optimize Refresh     YES
    List of values definition
    SELECT DISTINCT MARGINING_ACCOUNT d, MARGINING_ACCOUNT r
    FROM MBRDATA.INTRADAY_MARGIN_MONITOR
    WHERE ORG_ID = :P15_MEMBERID
    ORDER BY 1The next level, COMMODITY, is set up as a cascading LOV. The parent is the ACCOUNT.
    Named LOV     
    Display Extra Values     
    Display Null Value     
    Cascading LOV Parent Item(s)     P15_MEMBERID,P15_ACCOUNTID
    Page Items to Submit     
    Optimize Refresh     YES
    List of values definition
    SELECT DISTINCT PHYSICAL_COMMODITY D, PHYSICAL_COMMODITY R
    FROM
        SELECT PHYSICAL_COMMODITY,
               DENSE_RANK() OVER
                ( PARTITION BY ORIG_CLEARER_NAME, MARGINING_ACCOUNT
                  ORDER BY RUNTIME DESC ) AS RUNTIME_RANK
        FROM RISKDM2.INTRADAY_POSITION
        JOIN MBRDATA.ORGANIZATION
            ON ( INTRADAY_POSITION.ORIG_CLEARER_NAME = ORGANIZATION.NAME )
        WHERE ORGANIZATION.ID = :P15_MEMBER_OR_TRADER AND
              MARGINING_ACCOUNT = :P15_MARGINING_ACCOUNT
    WHERE RUNTIME_RANK = 1The next level, EXPIRY, is set up as a cascading LOV. The parent is the COMMODITY.
    Named LOV     
    Display Extra Values     
    Display Null Value     
    Cascading LOV Parent Item(s)     P15_MEMBERID,P15_ACCOUNTID,P15_COMMODITYID
    Page Items to Submit     
    Optimize Refresh     YES
    List of values definition
    SELECT DISTINCT EXPIRY_DATE AS D, EXPIRY_DATE AS R
    FROM
        SELECT EXPIRY_DATE,
               DENSE_RANK() OVER
                ( PARTITION BY ORIG_CLEARER_NAME, MARGINING_ACCOUNT
                  ORDER BY RUNTIME DESC ) AS RUNTIME_RANK
        FROM RISKDM2.INTRADAY_POSITION
        JOIN MBRDATA.ORGANIZATION
            ON ( INTRADAY_POSITION.ORIG_CLEARER_NAME = ORGANIZATION.NAME )
        WHERE ORGANIZATION.ID = :P15_MEMBER_OR_TRADER AND
              MARGINING_ACCOUNT = :P15_MARGINING_ACCOUNT AND
              PHYSICAL_COMMODITY = :P15_PHYSICAL_COMMODITY
    WHERE RUNTIME_RANK = 1Any ideas? I know I am just doing something dumb but, with me, I require and more specific example of my dumbness.
    Thanks,
    -Joe

    Hi Joe,
    looks like you don't reference the parent lov's items in the sql queries for ACCOUNT, COMMODITY and EXPIRY.
    Are there any processes (DA, Ajax etc.) that you use to populate the items :P15_MEMBER_OR_TRADER, :P15_MARGINING_ACCOUNT and :P15_PHYSICAL_COMMODITY in those queries?
    regards,
    Erik-jan

  • 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.

  • Bind variable problem in cascading LOVs

    Hi,
    after upgrade from APEX 3.0 to 3.1 all my cascading LOVs stopped working correctly. First level LOV is OK, but the second level LOV, which contains a bind variable in its SQL code, fails. Debugging shows that the bind variable referrencing to the value of the first level LOV is empty. It has worked without problems in 3.0. The bind variable format is traditional :ITEM
    This is an example of the LOV SQL:
    SELECT PSKUP_CZ display_value, ID return_value
    FROM PSKUP
    WHERE sk_id = :P1_SKUP
    ORDER BY 1
    Where :P1_SKUP refers to the vaule of the top level LOV.
    In Oracle® Database Application Express Release Notes Release 3.1 in chapter "3 Open Bugs and Known Issues", I've only found a short remark called "Problems with Queries Containing a Bind Variable and a String with Two Dashes". The recommended solution here was to use v('P18_X') instead of :P18_X
    I tried that but with no effect on my problem.
    Anybody has similar experience? Any workarounds?
    Thanks in advance,
    Zdenek

    Hi Zdenek,
    DV, NV, V are an optional component of the ApexLib framework. Actually they don't have anything to do with the framework itself.
    Because of the nature of this functions they have to have a hard coded reference to the FLOWS_XXX schema, but which causes problems if APEX is upgraded to a new version and the functions are not altered.
    I will probably removed them from the installation instructions or add a big remark that they have to be altered after an upgrade, because this kind of threads are re-occurring after each new released APEX version.
    Thanks
    Patrick
    My APEX Blog: http://inside-apex.blogspot.com/
    The APEX Builder Plugin: http://builderplugin.oracleapex.info/ New
    The ApexLib Framework: http://apexlib.sourceforge.net/

Maybe you are looking for

  • How to calculate Average balance for an account

    Hi, How to calculate average balance for an account for a particular period say for JAN-12 period and after the end of that period for another two days 01-feb-12 and 01-feb-12 ? I'm using the following query : SELECT cc.segment1||'-'||cc.segment2||'-

  • Query about TABSTRIP Control within Sub screen

    Hi Expert, I have requirement like follows: In IW32->Enhancement Tab screen is as subscreen and No: 0900. Now I want to have 2 different sub screen say 0910 and 0920 each of this for different purpose according to Order Type as per clients requiremen

  • How many parameters can function at the same time?

    Post Author: leongcy23 CA Forum: General Dear all, I have a situation where I need to use about 6 parameters in a report. In the Record Selection Formula Editor of the main report, I put "OR" for every parameters, which mean I can select either one o

  • CD Player in Director

    Hi I am creating an autorun title screen in Director for an audio CD. I want to be able to, inside the project, click the "play cd" button, and the audio will play inside the project. There is a DVD controller that does what I want, except that it's

  • Cbo problem

    10053 report: BASE STATISTICAL INFORMATION Table Stats:: Table: TEMP Alias: TEMP #Rows: 1000 #Blks: 3 AvgRowLen: 15.00 Table Stats:: Table: TEST_DEFAULT Alias: T #Rows: 1156944 #Blks: 1891 AvgRowLen: 7.00 Index Stats:: Index: I_TEST_DEFAULT_1 Col#: 1