Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
6 years ago
Solved

Power Query Editor Restricted at 1000 Rows - Doesn't pull in new arrays added to JSON

Hello, I am currently pulling in JSON data into PowerBI. Since the early this year we have added 2 new arrays to the data structure, which are way past the 1000 row limitation that the wizard uses. When I try to manually add the new arrays in the Power Query advanced editor, I get the following error:

Expression.Error: We expected newColumnNames to have the same number of items as fieldNames.
Details:
[List

 

Is there a way around this?

  • Not sure if my understanding is correct, but sometimes PQ autogenerates code that requires manual ammendments to typed in twice. So if you expand a record column for example, the following code will be generated:

     

    Table.ExpandRecordColumn(#"Filtered Rows", "Value", {"streetAddress", "city", "state", "postalCode"}, {"streetAddress", "city", "state", "postalCode"})

     

    The list in the last parameter is optional (new column names, if needed). So you can safely omit it if you want to stick with the original field names. 

    BUT if you include more columns to expand, you have to add a name for those columns as well in the last parameter:

     

    Table.ExpandRecordColumn(#"Filtered Rows", "Value", {"streetAddress", "city", "state", "postalCode", "country"}, {"streetAddress", "city", "state", "postalCode", "country"})

     

    Otherwise your error message will be shown.

2 Replies

  • ImkeF's avatar
    ImkeF
    Community Champion

    Not sure if my understanding is correct, but sometimes PQ autogenerates code that requires manual ammendments to typed in twice. So if you expand a record column for example, the following code will be generated:

     

    Table.ExpandRecordColumn(#"Filtered Rows", "Value", {"streetAddress", "city", "state", "postalCode"}, {"streetAddress", "city", "state", "postalCode"})

     

    The list in the last parameter is optional (new column names, if needed). So you can safely omit it if you want to stick with the original field names. 

    BUT if you include more columns to expand, you have to add a name for those columns as well in the last parameter:

     

    Table.ExpandRecordColumn(#"Filtered Rows", "Value", {"streetAddress", "city", "state", "postalCode", "country"}, {"streetAddress", "city", "state", "postalCode", "country"})

     

    Otherwise your error message will be shown.

    • Anonymous's avatar
      Anonymous
      Not applicable

      Thank you this worked