Optimizing Report Export Performance (Column Data)

Including column details (translations and number formats) via the `p_include_columns` parameter significantly impacts performance because it forces the database to perform an extra step for every report being exported . The database must explicitly parse all exported report SQLs in order to identify every single column name included in the query . This process is computationally intensive, especially for complex or voluminous SQLs, leading to a substantial slowdown of the export utility .

You should only use the `p_include_columns` option if you have mandatory column configurations to migrate . Specifically, this includes cases where you have defined optional multi-language column translations or implemented column-specific number format settings that differ from the site or report defaults . If your environment only uses default formats or English column headers, you should omit this option .

Custom number formats are defined in the lookup `XXEN_REPORT_NUMBER_FORMATS` . This lookup stores the internal Microsoft style IDs, which must be a numeric value above 200 (as lower IDs are reserved for Microsoft’s standard formats) . Once defined, you can reference these formats either for all columns in a report, or for individual columns using column translations .

Yes, for updating SQL text or List of Values across all reports simultaneously, you must use the Mass Change functionality, accessible via Blitz Report Setup > Tools > Mass Change . This utility allows you to enter a find-and-replace update across the entire SQL base . Always use the Preview button first to see the list of changed objects before applying the changes .