How to handle multiple dimension records having the same name even though they have unique key/relation with the fact table (1:M)? [closed]

Question

Closed. This question needs to be more focused. It is not currently accepting answers.

Want to improve this question? Guide the asker to update the question so it focuses on a single, specific problem. Narrowing the question will help others answer the question concisely. You may edit the question if you feel you can improve it yourself. If edited, the question will be reviewed and might be reopened.

Closed last year.

The community reviewed whether to reopen this question last year and left it closed:

Original close reason(s) were not resolved

Improve this question

I'm looking at Product dimension table.

It has got products table obtained by performing a SQL UNION between Product tables in 2 databases. The columns are: Dbname,productid,productname,productcategory

The same product name exists in both databases but with different ID. The unique key of this table is concat(dbname,productid).

Similarly, the sales table is created using the UNION approach and is related to product table on dbname,productid.

I have brought the product and sales tables into the power bi data model, and created a new column in both tables called key (concat dbname,productkey). And then created a relation on the dbname.

The product name duplicating isn't something I have ever seen before in any Product dimension table. So I wanted to get some guidance. — variable
– variable, Commented Aug 9, 2024 at 16:41
Yes the id (concat of dbname and productid) is unique and this is linked to the fact table. The key is not an issue. Just that I've never experience product names repeating in the past. — variable
– variable, Commented Aug 10, 2024 at 2:37

davidebacci · Accepted Answer · 2024-08-10 09:35:30Z

1

This is similar to the situation where multiple customers have the same name. The default situation is for PowerBI to aggregate common values together. e.g. the following table:

when placed in a table visual looks like this.

Even though there are two John Smiths who are separate people, they have been aggregated. To avoid this, set a key on the table and a row value like this:

When you add the same columns to a table, they will now be separate.

answered Aug 10, 2024 at 9:35

davidebacci

31.4k4 gold badges20 silver badges48 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

variable Over a year ago

The above screenshot of properties is of the table visual or the table in the model?

davidebacci Over a year ago

Table in the model

variable Over a year ago

Should the key be the productid? Or the concatenated key (dbname, productid)

davidebacci Over a year ago

Whatever represents your unique key in the table

Collectives™ on Stack Overflow

How to handle multiple dimension records having the same name even though they have unique key/relation with the fact table (1:M)? [closed]

1 Answer 1

4 Comments

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

4 Comments

Related