How to transpose json data for power bi, tableau, and looker import
- Step 1Flatten nested JSON before transposing — If the JSON array contains nested objects (address.city, metrics.revenue), use the JSON Flattener first to produce flat objects. Transposing flat objects produces clean column arrays.
- Step 2Transpose the flat array — Paste the flattened JSON array and transpose it. The output is an object with one array per column — matching the columnar structure BI tools expect.
- Step 3For Power BI: use JSON connector — In Power BI Desktop, use Get Data →’ JSON. Power BI's JSON connector reads list-of-records format. If using the columnar output, convert it back using List.Zip in Power Query M, or use the flattened row-oriented JSON directly.
- Step 4For Tableau: save as CSV — Paste the transposed output into the JSON to CSV tool to produce a CSV file. Tableau's CSV connector handles large files more reliably than its JSON connector for complex shapes.
Frequently asked questions
Should I transpose to columnar or keep the row-oriented format for Power BI?+
Keep the row-oriented format (array of objects) for Power BI's JSON connector. Power BI's Power Query engine handles the row-to-column mapping internally. The columnar transpose is most useful for chart libraries and Apache Arrow. For Power BI, flattening nested objects is more valuable than transposing.
What if my JSON has too many nesting levels for Tableau to parse?+
Tableau's JSON connector has limited support for deeply nested JSON. Flatten the JSON using the JSON Flattener before importing — this reduces deep nesting to flat dot-notation keys. Then convert to CSV for the most reliable Tableau import.
Is the business data transmitted to JAD Apps?+
No. Transposition runs entirely in your browser. Revenue data, business metrics, and operational records are never transmitted to JAD Apps servers.
Privacy first
Conversion runs locally in your browser. No file is uploaded — only metadata counters are saved for signed-in dashboard stats.