Creating multiple relationships

[Espen1515]

Hi,

I am having trouble creating the proper relationships between my tables. I have four separate tables, and my problem is connecting them in the same way. I am pretty new to Power BI, so I believe the problem is due mostly to my lack of basic knowledge. I have made a mock-up example below.

Project table: Project number is a unique value

Package table: The package number is unique to a project, but could occur more than once in the table (just not more than once per project)

Package shipment table: The shipment number is unique

Package shipment details table: The shipment item is unique per shipment number

So if I try to establish relationships here, for example "Count of shipment items on package number A on Project 1, I am not able to set this up. Any tips? I have managed to establish the relationship between Project number in all tables, but don't know how to handle the fact that package number is Unique per project.

With kind regards,

Espen Lütken

[Anonymous]

---

@Espen1515 wrote:

So if I try to establish relationships here, for example "Count of shipment items on package number A on Project 1, I am not able to set this up. Any tips?

---

@Espen1515,

Does the following measure return your expected result?

Measure = CALCULATE(COUNT('Package shipment'[Shipment number]),FILTER('Package shipment','Package shipment'[Project number]=1 && 'Package shipment'[Package number]="A"))

Regards,
Lydia

[Espen1515 · Accepted solution]

Hi Lydia,

Thanks for your reply!

My question is not really concerning getting up that measure that I used as an example, but about how to establish a relationship between these tables. In reality these tables have thousands and thousands of lines and I need to be able to make counts, measures, etc. appear by themselves as soon as I filter. And to do that the tables need to have relationships between them. 🙂

[Greg_Deckler]

I am thinking that you will need to create a table of unique Project/Package codes.

[Espen1515]

Hi, I am not quite sure what you mean. Isn't that what the Package table already does? There is a unique package on each project, but can as I say occur more than once in the table as it can occur on a second project.

For example, on Project 1 there is only 1 unique package called "Furniture", but Furniture can also occur in Project 2. But maybe you mean something else. Is it possible to be more specific? Or include a short description of what a table like that would like like as opposed to those that already exist?

Thanks!