Fixing guardrail warnings on report definitions

General
, , ,
1

I have a report definition that in filter conditions

  1. I have to uncheck use null if empty to display results if a value is not passed to a parameter

e.g: In a data type that contains products a column will contain whether the product is banking or insurance. If a value is not passed to this parameter it should display both banking and insurance products.

  1. Make a relationship to Contains

e.g: there are some products that will be applicable to banking and insurance. In this case I’m setting the column value to “Banking, Insurance”. Therefore depending on if the parameter value is passed as banking or insurance it will display this record as well along with other respective banking or insurance products.

However, the above options are creating guardrail warnings and the client wants to get rid of them. Is there any workarounds that we can do to fix those warnings?

Otherwise what are the recommendations for scenarios like this where the functionality provided raises guardrail warnings, but we need those functionalities?

2

@IshanT70

.You can call your RD within a data page. You can keep the “equal” filter condition in the report and maybe do the “contains” and other filter check in response data transform inside the data page

3

@IshanT70

I recommend justifying the guardrail warning if those 2 use cases are implemented per your business requirements.

Justify a warning to explain why your application is exempt from a best practice or guardrail. Documenting which warnings are intentionally unresolved can improve your compliance score.

Another suggestion: Please ensure the search columns are indexed to minimize the impact on the performance.