Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Sign up nowGet Fabric certified for FREE! Don't miss your chance! Learn more
Hi
My Data is a table that has two column's, a user name and their type. I want to take this information and flip it so I have new columns based on the User Type values, in my case there are just two. The Pivot options works, I get the headings, but as i don't add any aggregation I get an error.
Start and Result table:
Start
Result
The smaller tabel is waht I am trying to aim for.
Chris
Solved! Go to Solution.
Hi @Anonymous ,
I believe this is due to the fact that your data configuration provides no relationship between the names for PQ to be able to assign them together on a single row under the new headings.
This thread explains it pretty well, I think:
One user suggests to add an index before performing the pivot which is actually pretty smart as it visualises the problem quite nicely:
You can see where PQ is struggling: it can't correctly allocate two names to the same row as they have no relationsip to one another in the original table.
Pete
Proud to be a Datanaut!
Hi @ccarpent ,
I believe this is due to the fact that your data configuration provides no relationship between the names for PQ to be able to assign them together on a single row under the new headings.
This thread explains it pretty well, I think:
One user suggests to add an index before performing the pivot which is actually pretty smart as it visualises the problem quite nicely:
You can see where PQ is struggling: it can't correctly allocate two names to the same row as they have no relationsip to one another in the original table.
Pete
Hi @Anonymous ,
I believe this is due to the fact that your data configuration provides no relationship between the names for PQ to be able to assign them together on a single row under the new headings.
This thread explains it pretty well, I think:
One user suggests to add an index before performing the pivot which is actually pretty smart as it visualises the problem quite nicely:
You can see where PQ is struggling: it can't correctly allocate two names to the same row as they have no relationsip to one another in the original table.
Pete
Proud to be a Datanaut!
Hi
Your right, I need to rethink the problem, thanks for the quick response.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 7 | |
| 4 | |
| 4 | |
| 3 | |
| 3 |
| User | Count |
|---|---|
| 12 | |
| 11 | |
| 11 | |
| 7 | |
| 6 |