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

LOV Query Logic: ID Column vs. Value Column Binding

Avatar photoCustomer Questions & Answers 5 replies

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?

5 replies

  • Support Enginatics

    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

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

  • Support Enginatics

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

  • Avatar photoCustomer

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

  • Support Enginatics

    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.

  • You must be logged in to reply to this post.