Preserving Leading Zeros in Excel Output

To prevent Excel’s automatic type detection from treating alphanumeric data with numeric content as a number, you must explicitly format the column output in the SQL to enforce text formatting . The workaround involves prefixing the column data with an equal sign and enclosing it in double quotes . The SQL should look like this: `’=”‘ || cii.serial_number || ‘”‘ serial_number` .

No, if you apply this specific SQL workaround and run the report in the recommended XLSX output format, Blitz Report is designed to automatically remove the redundant prefix (`=”`) and suffix (`”`) characters from the data upon generation . This ensures the content displays correctly as alphanumeric text in Excel .

The documentation specifies that the automatic removal of the prefix/suffix characters (`=”` and `”`) occurs when the report is run in XLSX output format . While CSV format also preserves alphanumeric data, the specific automated cleaning process is noted for the XLSX format . If using CSV, you should verify if the raw CSV output still retains the extra quotes/equals signs.

Yes, the maximum column width for Blitz Report XLSX output files is controlled by the profile option ‘Blitz Report XLSX Max Column Width’ . The default maximum column width is 60 .