Executing BI Publisher Data Triggers in Blitz Report

Yes, Blitz Report fully supports leveraging this logic using the BIP Code field in the report header . When you populate this field with the BI Publisher data definition code, Blitz Report is configured to execute the dataTrigger section (e.g., `beforeReportTrigger`) of the associated data definition XML template . This allows the GTT to be populated by the pre-processing logic, and your Blitz Report SQL can then extract the data directly from the GTT .

You can quickly download and review the data definition XML template . This is achieved by double-clicking onto the BIP Code field within the Blitz Report setup window , . This action initiates a download of the associated XML file, allowing you to confirm the `dataTrigger` section logic .

If you are migrating existing BI Publisher reports in bulk, you should use the Import API . The procedure `XXEN_API.IMPORT_CONCURRENT_PROGRAM` programmatically imports the BI Publisher report, including its parameter definitions, and sets up the corresponding Blitz Report entry . However, the core report extraction SQL will need to be verified to ensure it correctly selects from the GTT populated by the `beforeReportTrigger` .

If a parameter’s default value starts with the keyword ‘select’, Blitz Report recognizes this and executes the SQL to dynamically derive the default value instead of treating the text as a fixed value . This is commonly used for defaulting dates (e.g., `select to_char(sysdate, ‘MON-RR’) from dual`) or retrieving user-specific information .