Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi there,
I am trying to create a table which pools information from another table but orders in a different way.
Below is the UserFieldValue table.
UserFieldValue | |||
RecordID | UserFieldID | UserFieldName | Value |
1 | 855 | Agency | Blue |
1 | 700 | Department | Black |
2 | 700 | Department | Yellow |
2 | 855 | Agency | Blue |
3 | 677 | Block | Green |
3 | 855 | Agency | Grey |
3 | 855 | Agency | Yellow |
4 | 677 | Block | Green |
4 | 955 | Custom | Red |
5 | 855 | Agency | Blue |
5 | 700 | Department | Blue |
5 | 650 | Bench | Black |
Using this data, I want to create a table that has primary key 'RecordID' and shows each UserFieldName as a column where the cells are the Values, and recordIDs with multiple inputs for a UserField show "Multiple Input":
RecordID | Agency | Department | Block | Bench | Custom |
1 | Blue | Black | |||
2 | Blue | Yellow | |||
3 | Multiple Input | Green | |||
4 | Green | Red | |||
5 | Blue | Blue | Black |
I have tried creating a table of unique IDs and then adding calculated columns using the below but this seems to just show Multiple Input for every single RecordID
selectedvalue is going to return the "Multiple Input" if the UserFieldValue[All_UserFieldValue] is blank OR there are multiple values so this may require more work.
However, the main problem is that the RecordID is not passed to the FILTER statement so it will be looking for userfieldid = 855 without the specific ID. So you can probably just add that in to the search clauses (&& UserFieldValue[RecordID] = thisTable[RecordID] )
--
Also the column seems to have 2 different names (value or All_userFieldValue)
The different value names are because I was simplifying the data for the sake of this post and missed an alteration..
But you're quite right! The FILTER did need specification on the recordid, have since adjusted:
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
21 | |
7 | |
6 | |
5 | |
5 |
User | Count |
---|---|
27 | |
10 | |
10 | |
9 | |
6 |