Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
I am trying to perform concatenate on a one to many relationship and I want to have no duplicate values.
CONCATENATEX(
FILTER('Table',[Site] = EARLIER([Site]) && [User] IN { "a", "b", "d" }),
[User],,""
)
I tried this and I end up with values like this:
id | user | wanted |
1 | a | aabd |
1 | a | aabd |
1 | b | aabd |
1 | d | aabd |
1 | c | |
2 | a | ab |
2 | b | ab |
2 | c | |
3 | a | ad |
3 | d | ad |
4 | c |
Here is a table representing what I would like.
id | user | wanted |
1 | a | abd |
1 | a | abd |
1 | b | abd |
1 | d | abd |
1 | c | |
2 | a | ab |
2 | b | ab |
2 | c | |
3 | a | ad |
3 | d | ad |
4 | c |
@Anonymous try this measure
C =
CONCATENATEX (
CALCULATETABLE ( VALUES ( con[user] ), FILTER ( ALLEXCEPT ( con, con[id] ), con[User] IN { "a", "b", "d" }) ),
[user], ","
)
I would ❤ Kudos if my solution helped. 👉 If you can spend time posting the question, you can also make efforts to give Kudos whoever helped to solve your problem. It is a token of appreciation!
Subscribe to the @PowerBIHowTo YT channel for an upcoming video on List and Record functions in Power Query!!
Learn Power BI and Fabric - subscribe to our YT channel - Click here: @PowerBIHowTo
If my solution proved useful, I'd be delighted to receive Kudos. When you put effort into asking a question, it's equally thoughtful to acknowledge and give Kudos to the individual who helped you solve the problem. It's a small gesture that shows appreciation and encouragement! ❤
Did I answer your question? Mark my post as a solution. Proud to be a Super User! Appreciate your Kudos 🙂
Feel free to email me with any of your BI needs.
I like this so much! It gets closer than ever. However, now I am finding the concatenated results are being considered distinct based on their order rather than their content. How would I go about resolving this level of distinction?
id | user | wanted | result |
1 | a | abd | abd |
1 | b | abd | abd |
1 | d | abd | abd |
1 | d | abd | abd |
1 | c | ||
2 | a | ||
2 | d | abd | adb |
2 | b | abd | adb |
3 | c |
@Anonymous I'm lost, what is missing between wanted and result?
Subscribe to the @PowerBIHowTo YT channel for an upcoming video on List and Record functions in Power Query!!
Learn Power BI and Fabric - subscribe to our YT channel - Click here: @PowerBIHowTo
If my solution proved useful, I'd be delighted to receive Kudos. When you put effort into asking a question, it's equally thoughtful to acknowledge and give Kudos to the individual who helped you solve the problem. It's a small gesture that shows appreciation and encouragement! ❤
Did I answer your question? Mark my post as a solution. Proud to be a Super User! Appreciate your Kudos 🙂
Feel free to email me with any of your BI needs.
ID 1:
wanted
abc
result
abc
ID 2:
wanted
abc
result
acb
This level of distinction recognizes a, b, and c are all unique and different. However the resulting calculation does not recognize abc and acb as the same.
@Anonymous I think it will be easier to sort the table in Power Query by user and it will fix itself.
Subscribe to the @PowerBIHowTo YT channel for an upcoming video on List and Record functions in Power Query!!
Learn Power BI and Fabric - subscribe to our YT channel - Click here: @PowerBIHowTo
If my solution proved useful, I'd be delighted to receive Kudos. When you put effort into asking a question, it's equally thoughtful to acknowledge and give Kudos to the individual who helped you solve the problem. It's a small gesture that shows appreciation and encouragement! ❤
Did I answer your question? Mark my post as a solution. Proud to be a Super User! Appreciate your Kudos 🙂
Feel free to email me with any of your BI needs.
User | Count |
---|---|
77 | |
77 | |
68 | |
67 | |
49 |
User | Count |
---|---|
108 | |
105 | |
93 | |
83 | |
64 |