32 chars · 2 lines
32 chars · 2 lines
32 chars · 2 lines
32 chars · 2 lines
CSV normalized-header troubleshooting
The header row contains role with leading whitespace and role with trailing whitespace. They look different as raw CSV text, but both normalize to role before JSON keys are created, so the converter rejects the collision. This tool is free to use. No account or payment is required.
Last updated
Treating role and role-with-a-space as distinct JSON keys would make generated data hard to use and easy to misread. The converter normalizes surrounding whitespace before enforcing uniqueness.
Rename the second normalized role column to access so both JSON keys remain distinct.
name, role,role
Ada,admin,ownername,role,access
Ada,admin,ownerCommon questions
CSV to JSON trims surrounding whitespace before using header cells as property names.
That would create fragile and visually ambiguous JSON keys, so VetaTool requires meaningful distinct names instead.
No. Only surrounding whitespace is trimmed; an internal space such as "display name" remains part of the key.
Debugging a specific CSV issue? Browse CSV troubleshooting.