Forum Discussion
Normalising nested json data
If you enable load the query becomes a partition and must be a flat table of simple column types. You need to disable load for the query "without destination". That will then be an expression rather than a partition.
Eventually your Power Query needs to produce a flat table with only basic column types. In Power BI Desktop columns containing records and lists and tables etc are ignored, but in the service they throw errors.
I see, but even if they dont have a destination?
There is a one to two relation in that im creating two tables from one json source.
So i have three queries in the power query. One query, without a destination, that reads in the json. Then two other queries that reference the first query to further flatten the data into the two seperate tables.
I figured this would be more efficient because the file is only read and parsed once for both destinations.
So each query in the power query needs to be flattened and type cast even if they dont have a destination?