Maxio exports structured CSV files that can be used for reporting, analysis, or integration with external tools. The exported data is structured for safe and reliable analysis. This article outlines best practices for parsing these files and explains how sensitive string values are sanitized to prevent spreadsheet-based execution risks.
How Maxio Sanitizes Exported Data
To protect your data when opened in spreadsheet tools, Maxio modifies any string value that begins with one of the following characters:
-
+(plus sign) -
-(minus sign) -
=(equals sign) -
@(at sign)
This is a precaution to prevent formula injection or malicious code execution. The change applies only to the exported CSV file, your underlying data in Maxio remains untouched.
Data sanitization affects only the export file. The original values stored in Maxio are never altered.
Parsing Exported CSV Files
We recommend identifying fields by their column headers (e.g., customer_email) rather than by position (for example, “column E”). Column order may vary depending on your export settings or if new fields are introduced.
Some exports, especially for Subscriptions, include optional fields such as:
- Custom fields
- Component data
- Estimated renewal amounts
- Last invoice totals
Always map data using column headers. Parsing by column position can cause failures if the export structure changes.
Customizing Export Fields
You can control which optional fields are included in Subscription exports under Config > Settings > CSV Exports. This applies to data such as components and estimated renewals.
To review every available field across export types, see the Data Export Field Reference.
Comments
Article is closed for comments.