Forum Discussion
Need help with table expansion
hi
Can somebody help me fix this problem
in query editor when I click on the table expansion icon below ...
It shows that the table has 17 columns which is correct
when I click OK , it expands the table BUT it does NOT display the first column from source file . The first column as shown below is the name of the source file. The second column shown below is the second column of source file. At the end it has created an additional 18th column which is null . Not sure why its happening . Any help would be appreciated
Anonymous
5 Replies
- lbendlinSuper User
According to your screenshot this works nominally. The "Name" column is there. Please explain your issue again.
- ashwinkolteHelper III2 seconds ago
The issue is this ==> "Data.Column1" in the above screenshot is second column of the source Table which I expand . what happened to first column ?
Basically on expanding the data i.e clicking on the expand icon , It is skipping the first column of the underlying data and instead creating a column with null values as last column in leau of the first column
- lbendlinSuper User
Please provide sample data (with sensitive information removed) that covers your issue or question completely, in a usable format (not as a screenshot). Leave out anything not related to the issue.
https://community.fabric.microsoft.com/t5/Community-Blog/How-to-provide-sample-data-in-the-Power-BI-Forum/ba-p/963216
Please show the expected outcome based on the sample data you provided.
https://community.fabric.microsoft.com/t5/Desktop/How-to-Get-Your-Question-Answered-Quickly/m-p/1447523
- ashwinkolteHelper III
The issue is this ==> "Data.Column1" in the above screenshot is second column of the source Table which I expand . what happened to first column ?
Basically on expanding the data i.e clicking on the expand icon , It is skipping the first column of the underlying data and instead creating a column with null values as last column in leau of the first column
- ashwinkolteHelper III
Hi .. The probelm is solved . There was an issue with the data . Have corrected it and now working fine. Thanks for your reachout .