Our exported incident management reports are missing several required fields that our auditors need to see. Specifically, the ‘Corrective Actions Taken’ and ‘Investigation Completion Date’ columns are blank in the CSV export, even though these fields are populated in the UI.
We’ve checked the export template configuration and both fields are selected for inclusion. The custom field exportability settings also show these as ‘Exportable’. Yet the exported file consistently has empty columns for these fields.
This is blocking our regulatory submission - we need complete incident records with all investigation details. We recently upgraded to qual-2023.1 and this worked fine in 2022.2. Is there an export schema patch we’re missing? Has anyone else encountered this after upgrading?
I remember seeing something similar. Check if those fields are ‘rich text’ fields in the database. Rich text fields sometimes need special export formatting enabled. Go to Admin > Data Fields > Incident Management and look at the field type for ‘Corrective Actions Taken’. If it’s rich text or HTML, there’s a separate setting to strip formatting for CSV exports.
You’ve hit a known issue with the 2023.1 upgrade. Here’s the complete solution addressing all three focus areas:
Export Template Configuration:
The 2023.1 upgrade doesn’t automatically migrate custom field mappings from 2022.2 export templates. You need to reconfigure the template:
- Go to Admin > Export Templates > Incident Management
- Click ‘Edit Template’
- In the ‘Available Fields’ panel, you’ll see ‘Corrective Actions Taken’ and ‘Investigation Completion Date’ listed but NOT checked (even though the UI shows them as selected - visual bug)
- Uncheck and re-check both fields to force the mapping to update
- For ‘Corrective Actions Taken’ (rich text field), enable ‘Strip HTML Formatting’ option
- Save the template
Custom Field Exportability:
The ‘Investigation Completion Date’ issue is related to how 2023.1 handles related record fields. This field is stored on the linked Investigation record, not the Incident record itself. To export it:
- In the export template editor, look for the ‘Related Records’ section
- Expand ‘Investigation’ relationships
- Find ‘Investigation Completion Date’ under the Investigation fields
- Check this field for export
- Set ‘Relationship Handling’ to ‘Include Primary Related Record’
This tells the export engine to join the Investigation table and pull that date field.
Export Schema Patch:
The grayed-out ‘Rebuild Export Schema’ button is a permissions issue. In 2023.1, this function requires the new ‘Data Schema Administrator’ role, which is separate from System Administrator. Here’s the fix:
- Go to Admin > Users & Roles > Your User Profile
- Add role: ‘Data Schema Administrator’
- Log out and back in
- Return to Admin > Export Templates > Incident Management > Advanced Settings
- Click ‘Rebuild Export Schema’ (now enabled)
- This process takes 2-3 minutes and rebuilds the field mapping cache
Important Note: After rebuilding the schema, you need to re-test your export template. Sometimes the rebuild process resets custom field selections, so verify all your required fields are still checked.
Validation:
After making these changes, export a small test set of incidents (5-10 records) and verify:
- ‘Corrective Actions Taken’ appears with text content (no HTML tags)
- ‘Investigation Completion Date’ shows actual dates
- All other required fields are present
If you still see blank columns, check the underlying incident records in the UI to confirm those specific incidents actually have data in those fields. Sometimes the issue is data quality, not export configuration.
For your regulatory submission, you may want to add a validation step to your export process: run a SQL query to count records with null values in critical fields before generating the final export. This helps catch data gaps early.
Brian, I found the ‘Rebuild Export Schema’ button but it’s grayed out. Does this require special admin permissions? I’m logged in as a System Administrator.
In 2023.1, they changed how related record fields are exported. If ‘Investigation Completion Date’ is actually stored on a related investigation record (not directly on the incident), you need to enable ‘Include Related Records’ in the export template. Otherwise the export only pulls fields from the main incident record itself.