Audit management findings export corrupted - formatting breaks in Excel output

QMS ETQ Reliance
, , , , , , , ,
1

We’re experiencing a critical issue with audit findings exports from our ETQ Reliance audit management module. When we export audit reports to Excel, the formatting breaks completely and several fields show corrupted data.

The main problems we’re seeing:

  • Long text fields in findings descriptions get truncated mid-sentence
  • Special characters (™, ®, accented letters) display as question marks or boxes
  • Multi-line comments collapse into single lines with odd spacing
  • The Excel template structure seems fine, but field mapping appears inconsistent

We’ve checked the export template configuration and character encoding settings, but can’t pinpoint the root cause. Our audit reports are unusable in their current state, which is blocking compliance reviews. Has anyone dealt with similar export corruption issues in ETQ’s audit module?

2

The truncation is likely hitting ETQ’s default text field export limits. In the export template XML configuration, you need to explicitly set the maxLength attribute for long text fields. Default is usually 255 characters. Also check if your Excel template cells have wrap text enabled - that helps with multi-line content preservation. Navigate to the template editor and look for the field definitions section where you can adjust these limits per field.

3

We had similar character encoding problems last year. The issue was that our export template was set to use Windows-1252 encoding instead of UTF-8. Go to Admin > Export Configuration > Audit Reports and check the ‘Character Encoding’ dropdown. Switch it to UTF-8 and test again. You might also need to adjust the field width limits in your template - ETQ has default character limits per cell that can cause truncation if your findings descriptions are lengthy.

4

For multi-line comment issues, check if your Excel cells have the ‘Wrap Text’ property enabled in the template. Also, ETQ sometimes converts line breaks differently depending on your export format settings.

5

Adding to Kevin’s point - you should also verify your field mapping in the export definition matches your Excel template column structure exactly. Misaligned mappings cause all sorts of formatting issues. Open your template file and count the actual columns, then cross-reference with the field mapping configuration in ETQ. Sometimes hidden columns or merged cells throw off the mapping sequence.

6

Thanks for the suggestions. I checked the encoding settings and found it was set to ISO-8859-1. Changed it to UTF-8 but still seeing truncation issues on long text fields. The character corruption is fixed though. Any ideas on the field length problem?

7

Let me provide a comprehensive solution addressing all the issues you’re experiencing:

Character Encoding Fix: Navigate to Admin Console > System Configuration > Export Settings. Change the character encoding from ISO-8859-1 to UTF-8. This resolves special character corruption (™, ®, accented letters). After changing, clear your browser cache and test the export again.

Text Field Truncation Resolution: The 255-character limit is a default export constraint. To fix this:

  1. Go to Admin > Export Templates > Audit Findings Template
  2. Edit the template XML or use the visual editor
  3. Locate text field definitions (Description, Comments, Findings)
  4. Set maxLength=“4000” for long text fields (ETQ supports up to 4000 characters in exports)
  5. Save and republish the template

Field Mapping Correction: Your Excel template structure must precisely match the export field sequence:

  1. Open your Excel template and document the exact column order
  2. In ETQ, go to Export Configuration > Field Mapping
  3. Verify each field maps to the correct column index (0-based counting)
  4. Pay special attention to hidden columns - they still count in the sequence
  5. Test mapping with a small dataset first

Multi-line Content Preservation: For comments and descriptions that span multiple lines:

  1. In your Excel template, select all data cells
  2. Enable Format > Alignment > Wrap Text
  3. Set row height to ‘Auto’ so content expands vertically
  4. In ETQ export settings, ensure ‘Preserve Line Breaks’ is enabled
  5. Use CHAR(10) as the line break character in export configuration

Additional Recommendations:

  • Create a backup of your current template before making changes
  • Test exports with sample data containing special characters and long text
  • Document your field mapping configuration for future reference
  • Consider setting up export validation rules to catch formatting issues early

After implementing these changes, your audit reports should export cleanly with proper formatting, full content preservation, and correct character rendering. The combination of UTF-8 encoding, increased field limits, accurate mapping, and proper Excel cell formatting will resolve all the issues you described.

8

I’ve seen this before. Check your field mapping configuration first - go to System Settings > Export Templates and verify that your text fields are mapped to Excel cells with proper formatting. Also, make sure your template has UTF-8 encoding enabled in the export definition properties.