The current implementation of the data export might produce invalid header value assignments. It happens for following scenario:
The lead data export is configured with a custom export (fields)
The form fields changed after first data sets were stored (New fields are added)
There is no lead containing the new form fields
To avoid the issue this PR does two things:
Retrieve the label from the database for fields having no data (and no custom label)
Does not skip columns without data
This PR threats the configured export fields as the determining configuration. Having an invisible field configured in the export configuration might be a valid use case if older records does contain the data for such fields.
The current implementation of the data export might produce invalid header value assignments. It happens for following scenario:
fields
)To avoid the issue this PR does two things:
This PR threats the configured export fields as the determining configuration. Having an invisible field configured in the export configuration might be a valid use case if older records does contain the data for such fields.