Full data export truncates Long Text Area fields if the object also contains compound fields
Last updated 13 days ago ·Reference W-3258792 ·Reported By 14 users
In Review
Summary
Weekly or monthly exports truncate Long Text Area fields to 255 characters if the object contains custom compound field types such as a Geolocation field.
Compound Field Considerations and Limitations
https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/compound_fields_limitations.htm
If you're unsure whether your organization may be affected by this please log a case with Salesforce Support who can verify via the details provided in this Known Issue's Internal Notes.
Repro
1. Create a custom Long Text Area (LTA) field and a custom compound field type such as a Geolocation field on the same object.
2. Create a record in this object and populate your LTA field with more than 255 characters.
3. Go to Setup | Data Management | Data Export and schedule a weekly export for the object.
4. Once the data export has completed unzip and open the CSV file for the object.
Actual Results: The LTA custom field is truncated to 255 characters.
Expected Results: The Data Export would not truncate the LTA field's contents.
Workaround
None unless an Administrator can remove custom compound field types from affected objects.
Alternatively, use Data Loader or a similar API client tool to extract and/or backup affected object's long text area field's data.
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.
