Home › Discussions › Questions & Answers › Validating Custom Development Code in Parameters
Customer · · Questions & Answers · 5 replies
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?
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.
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.
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.
What is the primary architectural recommendation for avoiding performance issues associated with optional parameters?
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.
Sign in with LinkedIn or Google to take part.
