Home › Discussions › Questions & Answers › Development Audit: Parameter Linkage to Report SQL

Development Audit: Parameter Linkage to Report SQL

Avatar photoCustomer Questions & Answers 5 replies

To ensure robust development, we need a mechanism to confirm that every parameter defined for a Blitz Report correctly points to an existing anchor placeholder in the main report SQL.

5 replies

  • Support Enginatics

    You must run the Blitz Report Parameter Anchor Validation report. This report checks if all parameter anchors exist in the `xxen_report_parameter_anchors` table.

  • What exactly is an ‘Anchor’ in the context of Blitz Report development?

  • Support Enginatics

    An Anchor is a placeholder in the report SQL where dynamic SQL (like a parameter’s WHERE clause) can be inserted at runtime, such as the `1=1` anchor.

  • If I’m using the anchor validation report, should I also check for parameter uniqueness?

  • Support Enginatics

    It is good practice. Use the Blitz Report Parameter Uniqueness Validation report to ensure there are no duplicate Blitz Report parameters.

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