Home Discussions Questions & Answers LOV Query Logic: ID Column vs. Value Column Binding

LOV Query Logic: ID Column vs. Value Column Binding

Avatar photoCustomer August 23, 2019 at 8:45 pm

I’m defining a custom LOV. It must select the columns ‘value’ and ‘description’. If I also include an optional ‘id’ column, which column is ultimately used to bind the parameter value (:bind_variable) during report execution?

Viewing 4 reply threads
  • Author
    Replies
    • Support August 25, 2019 at 7:06 pm  

      The LOV query must select the two mandatory columns ‘value’ and ‘description’, and it may include an optional ‘id’ column at the beginning of the select clause. If the optional ‘id’ column is included, this value is used as the parameter’s :bind value for report execution.

    • Avatar photoCustomer August 26, 2019 at 7:51 pm  

      And if the ‘id’ column is *not* included?

    • Support August 28, 2019 at 6:18 pm  

      If the ‘id’ column is not selected, then the ‘value’ column is used to bind the parameter restriction for report execution.

    • Avatar photoCustomer August 30, 2019 at 1:08 am  

      If I create a parameter of type LOV Custom, can I modify the LOV query there directly without affecting other reports?

    • Support August 30, 2019 at 6:49 am  

      Yes, if you use parameter type LOV custom, the ad hoc LOV query you define is unique to that parameter and will not affect any other reports.

Viewing 4 reply threads
  • You must be logged in to reply to this post.

Login with: