Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM. Register now.

Reply
trevorho
Frequent Visitor

Modelling multi valued fields

Hi Community.

I have a bit of a modelling challenge related to how to handle multi value fields captured on the source system. Users capture fields for a ticket record. The majority of fields are single value type fields so this makes it easy to create a ticket dimension with each field as an attribute on the dimension. Until multi value fields come along! Let’s assume we have two multi value fields - there are more but let’s keep it relatively simple first. The two multi valued fields are Team and Error Type. The user can leave each blank, or populate one or  many selections. So in the worst case scenario there might be 3 teams (A, B, and C) and 4 error types (1, 2, 3, and 4) selected and they are not related to each other. I have modelled this as a fact table with a ticket key for the ticket dimension and a ticket category key for the ticket category dimension. The ticket category dimension  has a category group (team or error type) and category value (A to C, 1 to 4). So basically the fact has 7 rows for the same ticket and the seven multi value selections from the source system.

My problem is that the users want to be able to filter by a multi value field, as in show me all tickets where Team B has been selected but at the same time also have one or more multiple value fields side by side on one row. In a more simple example of one team and one error type being selected it comes out as two rows in the cube,  the first showing the team and blank for error type and the second row showing the error type and blank for the team.

My current line of thought is to keep the individual category fields, e.g Team and Errorv type as filter fields and then creating 6 separated fields for placement as rows. That way it will show one ticket row with two fields for “Team selections” and “Error Selections”.

Thoughts anyone?

 

Thanks 

Trevor

2 REPLIES 2
trevorho
Frequent Visitor

Sure, this is made up data:

  • Ticket "TKT001" is captured with amongst other fields, Teams (A, B, and C) and Error Types (1,2,3,4)
  • Ticket 'TKT002" is captured with amongst other fields, Teams (A) and Error Types (1)

My two dimensions:

DimTicket

TicketKeyTicketCodeOther fields
1TKT001Blah Blah
2TKT002More blah blah

 

DimTicketCategory

TicketCategoryKeyTicketCategoryTicketCategoryValue
1TeamA
2TeamB
3TeamC
4Error Type1
5Error Type2
6Error Type3
7Error Type4

 

Fact Table

TicketKeyTicketCategoryKey
11
12
13
14
15
16
17
21
24

 

This is the view they want:

Filter: Team

Filter: Error Type

 

Ticket NoTeamError Type
TKT001A,B,C1,2,3,4
TKT002A1

while still being able to filter for individual teams or error types

 

My current view looks like this :

Ticket NoTeamError Type
TKT001A 
TKT001B 
TKT001C 
TKT001 1
TKT001 2
TKT001 3
TKT001 4
TKT002A 
TKT002 1

 

Hope this makes sense

Trevor

v-chenwuz-msft
Community Support
Community Support

Hi @trevorho ,

 

Please half of it is understandable, but the second half is not quite clear what you want the result to look like, can you draw it or show it in excel? If possible, please attach the example data.


Best Regards

Community Support Team _ chenwu zhu

Helpful resources

Announcements
October Power BI Update Carousel

Power BI Monthly Update - October 2025

Check out the October 2025 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Kudoed Authors