Blocker
Export is disabled because a complete, trustworthy result cannot be produced.
Transparent conversion rules
Data quality checks, defined before you rely on them
DataFormatKit separates failures that block export, risks that need review, and deliberate transformations that belong in an audit trail.
Warning
Conversion can continue, but a value or structure deserves human review.
Choice or change
A user-selected or protective transformation is counted and described.
Current check catalog
What each finding means
01
Blocker
Invalid or unsafe source structure
Malformed JSON, XML, or delimited text must be corrected before export. JSON duplicate keys and XML DTD or custom entity declarations are blockers because continuing would hide ambiguity or create a parsing risk.
02
Blocker
Row and input limits
The first release accepts up to 10 MB of source data and 50,000 result rows. Expansion can create more rows than the source visibly contains, so the result limit is checked after structure choices are applied.
03
Warning
Long or unsafe numbers
JSON integers with 16 or more digits and numbers outside JavaScript's safe integer range can lose precision in ordinary parsers. DataFormatKit retains the original number text and writes these values as Excel text cells.
See the long JSON integer guide →04
Warning
Leading-zero identifiers
Values such as postal code 02108 or account ID 000123 are usually identifiers, not quantities. They remain text, although CSV itself cannot force a spreadsheet application's import type.
See the leading-zero CSV guide →05
Warning
Spreadsheet formula-like values
Cells beginning with =, +, -, @, tab, or carriage return may be interpreted as formulas by spreadsheet software. CSV export protects these values by default.
06
Warning
Missing and uneven fields
A missing source field is different from an explicitly empty value. Uneven delimited rows and sparse object records are retained as visible missing cells rather than silently dropped.
07
Choice
Nested array representation
An array can remain JSON text, scalar arrays can be joined, or one selected JSON array can expand into rows. Multiple arrays are never multiplied automatically because a cross product can change record meaning.
08
Choice
Record path and delimiter
Candidate JSON arrays, repeated XML nodes, and detected text delimiters are shown for confirmation. Automatic detection provides a starting point, not a hidden promise of semantic correctness.
See the XML record-node guide →Downloadable evidence
What the conversion report contains
The report is a JSON companion file for people who need to explain how an output was produced. It does not certify that the source meaning is correct.
sourceFormatThe parser used for the conversion.
rowCount / columnCountThe complete result dimensions, not just the preview.
issuesBlockers, warnings, counts, and representative row references.
changesGenerated names, array choices, formula protection, and other recorded transformations.
metadataEncoding, detected delimiter, record path, and available structural choices when relevant.
createdAtThe browser time when the report was generated.
See the checks in context
Try a sample with an intentional risk.
The JSON example includes long numeric identifiers; the text example includes leading zeros and a formula-like value.