Where is "Display as Text (based on LOV, saves state)"

I am developing an application using the version of HTMLDB that comes with OracleXE.
I have a tabular form, in which the default column for a particular item is sourced from a previously entered item on another page. This is a lookup item and needs to be non-changeable by the user. So I want to use the "Display As" option "Display as Text (based on LOV, saves state)". However, this option is not available in the pull-down for "Display As". The option "Display as Text (based on LOV, does not save state)" is available, but using this option means that the item is not saved to the database.
Does anyone know why the stateful display as option is not available.
Thanks in advance,
Rob

Scott, thanks for the feedback. The problem is that although the value is displayed correctly, it is NOT saved to the database. Effectively, header information is entered in a previous screen, and one of the entered fields is written to each of the detail lines associated with the header. We are re-platforming an existing application (written in an obscure form of basic), and at this stage changing the schema is not an option. So this header item (which is a foreign key to a "store" table), is meant to be written down to each line, on the screen displayed as the store name, and written to the inserted lines as the lookup id. If I use the dispaly as text save state option teh database is updated correctly, but displays the id rather than name on the screen. The only display as lov option i can see is the one that does not save state. If I use this option the screen displays as I want but the database is not updated. I need to use the display as lov saves state option. but i do not see it.
Any ideas?
Thanks for your time.
Rob

Similar Messages

  • Cannot see Display as Text (based on lov, saves state)

    I have raised this question on the HTMLDB forum (Where is "Display as Text (based on LOV, saves state)" but in case its XE specific I am posting here too.
    I have a tabular form in the XE version of HTMLDB, and wish to use the "Display as Text (based on LOV, saves state)" option. However, this option does is not available to me - are there some conditions necessary for this option to be displayed?
    Thanks, Rob

    Rob,
    I doubt it's an XE specific issue. I've asked for more information in the original thread.
    Sergio

  • Annoying [ ] with "Display as Text (based on LOV, saves state)"

    Hi all,
    I've got a form where some items are shown as “Display as Text”. These values are displayed normally.
    But I also have some items which are shown as “Display as Text (based on LOV, saves state)”. When I run the page and these items don't return a value (because it isn't filled in in another page), we get the annoying []-sings.
    Is there anyone who knows how to fix this, I just want to display nothing when there is no value.

    I've tried this one already.
    I tried to leave it blank, & nbsp ; , text,... but the problem is that our lov is build by a function and it always returns a query, so the LOV is never null.
    I figured something out: made a process after header that has some cursors to get the values from the database and changed the item to a simple display as text-field. There were only 4 that were wrong, so it wasn't to much work.

  • Display As Text (based on LOV, saves state)  "p_t03" was assigned by APEX

    Hi All,
    I have an ITEM
    Name: P36_INT
    Display As: Display As Text (based on LOV, saves state)
    Output in my HTML:
    [input type="hidden" name="p_t03" value="YES" />[span id="P36_INT">Interior[/span>
      'p_t03' was assigned by APEX
      In my Javascript I have to access it as the following to get the "YES" value:
      var lintObj = html_GetElement('p_t03');
      Originally it was 'p_t01' but it changed from 'p_t01' to 'p_t03' somehow.. out of my control.
      How do I assign an ID or assign my own name to the "hidden" item?                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    Scott, thanks for the feedback. The problem is that although the value is displayed correctly, it is NOT saved to the database. Effectively, header information is entered in a previous screen, and one of the entered fields is written to each of the detail lines associated with the header. We are re-platforming an existing application (written in an obscure form of basic), and at this stage changing the schema is not an option. So this header item (which is a foreign key to a "store" table), is meant to be written down to each line, on the screen displayed as the store name, and written to the inserted lines as the lookup id. If I use the dispaly as text save state option teh database is updated correctly, but displays the id rather than name on the screen. The only display as lov option i can see is the one that does not save state. If I use this option the screen displays as I want but the database is not updated. I need to use the display as lov saves state option. but i do not see it.
    Any ideas?
    Thanks for your time.
    Rob

  • Display as text (based on LOV saves state) : possible border ?

    Hi,
    Like mentioned in the subject, I have many Display as text (based on LOV saves state). I would like to have a frame or a border around this field eventhough it's read only, like a regular field. How can I do that ?
    thank you.

    Depending on your visual requirements, you could change the items to Text Fields (disabled or not) then simply make the Read-Only atttribute set to "always" or something that would equate to "always". It would look just like a text field (since it would in fact be one), but would be read-only.
    Sadly, this would require you to change all your items to the new type which would take time.

  • Display as text (based on LOV) not working

    hi --
    I've not used this kind of item before, so there's probably some really simple thing I'm missing....
    Have the LOV:
    select objecttype_name display_value, objecttype_id return_value
    from hdb_objecttype_syn order by 1
    Return value is going into page item :P3_objecttype_id (a popup LOV). Have another item, :P3_objecttype_name, which is a display as text (based on LOV) item. When/how is this item supposed to get populated? When I select a value from the LOV, I'd expect the text item to be set to the display value of the LOV, but it is always []. The source type of :P3_objecttype_name is Sql Query, and the query is:
    select objecttype_name from hdb_objecttype
    where objecttype_id = :P3_objecttype_id
    Does the page have to be submitted before the display item is populated? Seems like that wouldn't be very helpful...
    Thanks,
    C

    HI Varad -- I'm afraid I'm new enough to all this to not know how to implement either of your solutions... and that's after scanning the forum for additional info.
    How do I get the page to submit? Is there any way to do this w/o forcing the user to explicitly press a button? (which would be way too much, as there are probably 10 LOVs on this page).
    If I choose to use javascript, 1) on what item and under what attribute do I put the script (is it on the objecttype_name that needs to be populated?), and 2) where can I find an example of what this might look like? I'm not familiar w/ it at all.
    My goal is ultimately to have an LOV that displays both the key value and the name (which I guess can be accomplished by concatenating those together in the LOV select statement), to return the name to the page, and then have the ID automatically filled in to match the key (the example I sent you is backwards, simply because I started building this page w/ only key values displayed, added the name as a test later.) And, I also want the user to be able to type in the ID (no LOV would be attached to it), and have the name automatically populated. I'm guess this could be accomplished in a way similar to having the name filled in after the value is chosen from the LOV... If I can just figure out how to do that!
    Thanks,
    Carol

  • Cascade LOV display as text (based on LOV) in clasic report

    Hi Experts,
    It is possible to use cascade LOV - item is displayed as text (based on LOV) in clasic report ? (Display AS)
    I would like to reference to another column displayed in the report in LOV.
    Example:
    select description d,
           val_strg2 r
      from domain_cntr
    where cntr_name = 'CH_PRIM_ST_NOTE'
       and val_strg1   = #PRIM_STATUS#
       and active_idc  = 'Y'#PRIM_STATUS# is the column i would like to reference.
    Is it possible ? IN CLASIC REPORT
    regards
    J :D

    Hi,
    >
    Is it possible ? IN CLASIC REPORT
    >
    Yes.
    It may a rather long thing to code, so be ready for it.
    Here is how:
    a. Use APEX_ITEM API in your Report Query. Make sure you specify the p_item_id parameter , using #ROWNUM#
    b. In the Parent LoV wrtie an onChange event trigger that fires a JavaScript function and pass the ID of the element .
    c. In this JavaScript function make an AJAX call to get the <select>...<option...>...</select> , in short the complete HTML of the child LoV
    d. Push this HTML fragment into the Child Lov. You construct the ID of the target based on the ID of parent . E.g. f01_0001 to f02_0001.
    e. You may additional keep the child invisible or disabled initially, and then make it visible/enable it after it is populated.
    Regards,

  • Display as Text based on LOV - formating

    I have a slight problem with
    Display as Text based on LOV report column formating.
    Whatever I try to enter, regardless where CSS Clas, CSS Style - formating simply
    doesn't work. The only formating that works is:
    Number / Date Format.
    Is there a solution for this?
    Thanks,
    Denes Kubicek

    I found a simple workarround and I will post it:
    1. Instead of using LOV I created a function that does the same
    ( using a cursor and returning a value )
    2. Since the field needed to act as a link, I used css to format the output
    and it worked just fine.
    Thanks,
    Denes Kubicek

  • Report "Display Text (Based on LOV)" columns don't like colons - Bug?

    This is a bit hard to explain in text, so I've built a sample app: http://apex.oracle.com/pls/otn/f?p=9608:1
    The app has two pages, which demonstrate two related bugs in the handling of Report "Display as Text (based on LOV)" columns.
    Basically, if the LOV query returns a string that contains colon characters (":") in the display column, the values are matched up correctly, but the colons are stripped from the display.
    If the LOV query returns a string that contains colon characters in the return value column, then the matching fails entirely.
    Removing the colon characters eliminates the problem.
    We actually ran into this in a production environment, after an upgrade from Apex 3.0.0 to 3.2.1. The behavior definitely did not occur in Apex 3.0, but was added at some point between the two versions.

    The colon is actually part of our data (the field in question is a URN namespace).
    And yes, I understand the function of the colon in Apex URL parameter passing. However, I wouldn't expect that sort of parsing to be used against the results returned from an LOV query.
    Also, the LOV is fine in of itself -- a select list based on the LOV displays & returns the expected values. It's only when I use a report column based on an LOV that this behavior creeps in.
    We've found a (fairly painful) workaround -- altering both the report query and the LOV query to to do something like replace(column, ':', '_') -- but that's a manual change to a large number of pages for us.
    This behavior is new to version 3.2.1. It didn't happen in version 3.0.

  • Display as text based on pl/sql - how to return value

    Hi,
    I have a item set as "display as text based on pl/sql". How do I get the PL/SQL anonymous block to return the value of the item?
    My function declares and populates a variable called t_output which is the value I want displayed in the item. The PL/SQL I have written is correct as I have tried it in SQLPlus* with DBMS_OUTPUT.PUT_LINE and I get the correct output, but I don't know how to set my item to the value of t_output. I have tried adding ":P73_ITEM := t_output;" into the end of the PL/SQL block.
    Thanks
    Lucy

    Hi Lucy,
    Try this and see.
    make the display as:display as text(saves state)
    source type: sql query
    in source value or expression type
    select func(arguments) from table name;
    Good luck

  • Convert numeric value to display as text based on record in another table? ASP/VB

    I have an orders table:
    orderID (PK)
    pickupname
    pickupaddress
    pickupregion (numeric)
    pickuppostcode
    deliveryname
    deliveryaddress
    deliveryregion (numeric)
    deliverypostcode
    I also have a regions table:
    regionID
    regionname
    On my ASP page, I would like to display the pickup and
    delivery addresses as
    follows, but also need this to be within a repeat region as I
    am displaying
    a number of orders on the page (I have wrapped what I want in
    the repeat
    region in dashes, below):
    ---------Repeat Region Start-----------
    Pickup Address:
    Name
    Address
    Region (pickupregion)
    Postcode
    Delivery Address:
    Name
    Address
    Region (deliveryregion)
    Postcode
    --------Repeat Region End------------
    As it displays at the moment, I get this (using sample data):
    ---------Repeat Region Start-----------
    Pickup Address:
    Joe Bloggs
    High Street
    12
    HT12 5TY
    Delivery Address:
    Jane Bloggs
    The Mall
    33
    DT6 5TG
    --------Repeat Region End------------
    Is there any way to convert these numeric values to the
    actual region name
    but to keep it within one recordset so that I can use the
    repeat region? I
    tried creating a recordset for regions (SELECT regionID,
    regionname FROM
    tblRegions WHERE regionID = pickupregion OR regionID =
    deliveryregion), but,
    because I'm not repeating this region, it just displays the
    same regional
    name for every order, albeit the first record returned does
    contain the
    correct values! :o)
    I was thinking about some kind of inner join, but it's having
    two numeric
    region fields in the orders table that is causing me
    headaches! PS. I need
    to keep the two addresses within one orders table - I had
    thought of that!
    Got me a bit stumped, I have to say. Any help would be
    greatly appreciated.
    Thanks.
    Regards
    Nath.

    I've tried this one already.
    I tried to leave it blank, & nbsp ; , text,... but the problem is that our lov is build by a function and it always returns a query, so the LOV is never null.
    I figured something out: made a process after header that has some cursors to get the values from the database and changed the item to a simple display as text-field. There were only 4 that were wrong, so it wasn't to much work.

  • Display required field based on LOV

    I have an application that has many required fields. One of the fields (P11_RANK) is populated from a LOV. I have a condition on this field when a specific item(s) is selected form the LOV, (:P11_RANK IN ('First-Year Student','Sophomore','Junior','Senior') an additional required field (P11_FACULTY_SPONSOR) is displayed on the form.
    Currently my application is working but the additional required field to be display and filled in does NOT display until after the SUBMIT button is pressed. The applicaiton user needs to fill in this addtional field and SUBMIT again. As you can imagine that causes a bit of confusion, even though I have explained this quirk in my application notes.
    I would like the field to display after I leave the RANK field. I think this is where javascript comes in, but I am new to javascript and the training I received did not cover this issue. I have looked at Carl Backstrom's examples, but I am still confused as to what needs to be done.
    Any help on this would be greatly appreciated.
    Joyce

    I found a simple workarround and I will post it:
    1. Instead of using LOV I created a function that does the same
    ( using a cursor and returning a value )
    2. Since the field needed to act as a link, I used css to format the output
    and it worked just fine.
    Thanks,
    Denes Kubicek

  • Display af:outputLabel based on lov selection

    hi i have a situation where i have lov which got two option GOVT,PRIV when the lov selection is GOVT,i what to display Responsible person(s)” in
    af:outputLabel and when lov selection is PRIV i what to display Ownership in af:outputLabel am in jdeveloper 11.1.1.6.0

    yes i figure it out
    <af:selectOneChoice value="#{bindings.Organisationtypecode.inputValue}"
                                            label="#{bindings.Organisationtypecode.label}"
                                            shortDesc="#{bindings.Organisationtypecode.hints.tooltip}"
                                            id="soc1" simple="true"
                                            autoSubmit="true" required="true"
                                            valueChangeListener="#{pageFlowScope.orgDetailsBean.valueChangedorgtype}"
                                            contentStyle="width:145px;">
                          <f:selectItems value="#{bindings.Organisationtypecode.items}"
                                         id="si1"/>
                        </af:selectOneChoice>
    <af:outputLabel value="Responsible person(s)" id="ol19"
                                        inlineStyle="color:Black; font-weight:bolder;"
                                        partialTriggers="soc1"
                                        visible="#{bindings.Organisationtypecode.inputValue eq '1'}"/>
    <af:outputLabel value="Ownership" id="ol20"
                                        inlineStyle="color:Black; font-weight:bold;"
                                        partialTriggers="soc1"
                                        visible="#{bindings.Organisationtypecode.inputValue eq '2'}"/>

  • Bug: Report Column based on LOV character string buffer too small error

    When using a column type of "Display as Text (based on LOV, does not save state)" with a result set that is rather large causes a character or string buffer too small oracle error.
    See the below page for an example.
    The example page below has a single report off a table called "HUGE_TABLE" which has two columns: display and code
    Code contains a number between 0 and 100000.
    Display contains the number in code appended to a block of text.
    When I display the report with no Display As Text (based on LOV does not save state) it displays fine.
    If I make the "Code" column display as text based on LOV and make the LOV
    "SELECT display, code FROM huge_table"
    I get the error you see on the page.
    http://apex.oracle.com/pls/otn/f?p=32149:1
    Thanks.

    Thanks for your help Scott.
    So from what I've gathered from my own tests and the discussions you linked me to the LOVs based on SQL queries are being converted into "static LOV" strings before being used.
    As such they are limited to the PL/SQL VARCHAR2 max size of 32767
    Which means given the static reduction of the string 'STATIC:' that we have 32760 characters left.
    Which is where your SUM( LENGTH( display ) + LENGTH( return ) + 2 ) comes in.
    In short, if:
    sum( length( display ) + length( return ) + 2 ) + 7 > 32767
    would evaluate to true then you have a problem. :)
    I'll use this to track down my problems and switch them over to inline queries.
    Thanks.
    Cheers,
    Joe

  • Urgent - Report Column based on LOV - Value not found in LOV

    Hi All,
    Recently, we have upgraded to HTMLDB 2.0 from HTMLDB 1.5.
    I have a SQL report. One of the columns is based upon LOV - Display as Text (Based on LOV, does not save state).
    For the "Ids" of the report, it should display the corresponding "Names" from the LOV.
    But, for the cases, where no record exist in LOV for some Id, then it is directly showing the Id instead of "-" (which i have specified in Display Null Text) in the report column attributes.
    Before upgrade, it was working fine.
    Any idea where is the issue.
    Please help.
    Thanks in advance,
    Monika

    Hi,
    Can anybody help me in sorting out this issue please.
    For your reference, i have made a test case on
    http://apex.oracle.com/pls/otn/f?p=20451:4:3519837362944582:::::
    Here, there are 2 tables
    1. MY_EMP_COUNTRY(emoid, empname, cntry_id)
    2. MY_COUNTRY_LOOKUP(id, name,active)
    LOV is created on table 2
    select name d, id r
    from my_country_lookup
    where active = 'Y'
    And, on the page a SQL report is created
    select empname, cntry_id
    from my_emp_country
    where, cntry_id is based upon the LOV.
    Since, in lookup table, cntry_id = 4 is set inactive, it is not picked up by the LOV and hence on the report instead of showing the NULL text it is showing the cntry_id (4).
    The attributes of report column cntry id -
    Named LOV = CNTRY_LOV
    Display Null = YES
    NULL text = -
    Display Extra Value = YES
    Am I missing anything.
    thanks,
    Monika

Maybe you are looking for