Home Discussions Questions & Answers Validating Custom Development Code in Parameters

Validating Custom Development Code in Parameters

Avatar photoCustomer March 23, 2024 at 5:32 pm

We use the `xxen_util.dff_columns` function in our parameters, but sometimes developers input the wrong Descriptive Flexfield (DFF) table name. Is there a validation report to catch these errors?

Viewing 4 reply threads
  • Author
    Replies
    • Support March 25, 2024 at 11:00 am  

      Yes, the Blitz Report Parameter DFF Table Validation report shows any parameters using the `xxen_util.dff_columns` function which reference an incorrect DFF table name.

    • Avatar photoCustomer March 26, 2024 at 5:48 am  

      We also need to check for potentially confusing scenarios where the same bind variable name is accidentally used across different parameters, or if multiple bind variables exist in one parameter’s SQL text.

    • Support March 27, 2024 at 1:56 am  

      Use the Blitz Report Parameter Bind Variable Validation report. This report checks which bind variables were assigned to which Blitz Report parameter, useful for detecting cases where the same bind variable name is incorrectly used in different parameters.

    • Avatar photoCustomer March 28, 2024 at 7:38 pm  

      What is the primary architectural recommendation for avoiding performance issues associated with optional parameters?

    • Support March 29, 2024 at 1:53 pm  

      It is recommended to use dynamic SQL anchors, such as `n=n`, instead of `nvl(:bind_variable, column_name)` coding for optional parameters to avoid performance issues.

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

Login with: