Home Discussions Questions & Answers Internal parameters not visible to users

Internal parameters not visible to users

Avatar photoCustomer December 21, 2019 at 2:58 am

I need a parameter that derives a value used internally in the SQL logic, but the user should never see or modify this field on the run window. How do I achieve this invisibility?

Viewing 6 reply threads
  • Author
    Replies
    • Support December 21, 2019 at 12:51 pm  

      You define this parameter using a negative display sequence number. Negative display sequence numbers are specifically used to define hidden parameters.

    • Avatar photoCustomer December 21, 2019 at 10:13 pm  

      What is the typical technical use case for such a hidden parameter?

    • Support December 22, 2019 at 3:08 pm  

      They are typically utilized to populate a &lexical anchor with dynamic SQL text before report execution. For example, the AR Transactions and Lines report uses a hidden parameter to dynamically generate a string for revenue account columns.

    • Avatar photoCustomer December 23, 2019 at 2:42 am  

      If I am debugging, can I force these hidden parameters to display temporarily?

    • Support December 24, 2019 at 5:40 pm  

      Yes, developers can show these hidden parameters for debugging purposes by setting the profile option ‘Blitz Report Show Hidden Parameters’ to ‘Yes’.

    • Avatar photoCustomer December 26, 2019 at 6:02 am  

      If I define a standard visible parameter, but I don’t give it a display sequence number, what happens?

    • Support December 28, 2019 at 2:11 am  

      If you have multiple entries for the same parameter name (e.g., to insert different SQL text at different positions), only one of them needs the display sequence, parameter type, and LOV setup. Subsequent lines for the same parameter name have the display sequence left blank.

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

Login with: