After a recent schema update to accommodate new custom fields in our audit module, the JSON export functionality is no longer including these custom fields in the output. Standard fields export correctly, but all custom fields (audit_risk_level, business_unit, compliance_framework) are missing from the JSON structure.
The export completes without errors, but the resulting JSON only contains the base schema fields:
{"auditId":"AUD-2025-001","status":"completed","auditDate":"2025-03-28"}
// Missing: audit_risk_level, business_unit, compliance_framework
We use these JSON exports for integration with our analytics platform, and the missing custom fields are breaking our downstream reporting dashboards. The XML export format includes all fields correctly, but our analytics tool requires JSON input.
I encountered this exact issue after adding custom fields to our change control module. The JSON serializer uses a whitelist approach for field inclusion. You’ll need to update both the export template AND the JSON schema definition file. The schema file is usually located in the config/export directory and needs to explicitly declare your custom fields with their data types.
Thanks for the pointers. I found the export template configuration, but I’m not seeing a clear way to add the custom fields to the JSON schema mapping. Is there a specific syntax or attribute I need to use for custom field definitions?
Custom fields in Arena use a different namespace than standard fields. In your JSON export template, you need to reference them using the ‘custom.’ prefix. So instead of just ‘audit_risk_level’, you’d use ‘custom.audit_risk_level’ in the field mapping configuration. This tells the JSON serializer to look in the custom attributes table rather than the base audit table.