Standard for choosing which join column to hide at report level?

[willayd]

Let's assume I have a model where a fact table and a dim table are joined together by a column called "Join Key" in both tables. The end user does want "Join Key" available for reporting, but it should only appear once.

Should I hide "Join Key" in the fact table or the dimension table? Or does it not matter?

[v-xicai]

Hi @willayd ,

You may hide "Join Key" in the fact table, in this way. And it matter. When you hide the column, the field now disappears from the view, but the data is still available on the report, and publish this up to the Power BI service, we can see the field remains hidden. Then when you edit the report without this hidden column appearing, you couldn't design the report using the column of fact table in Power BI Service ,

Best Regards,

Amy 

Community Support Team _ Amy

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[TomMartens · Accepted solution]

Hey @willayd ,

it's very common to hide the columns that are used for joining are hidden in the fact table.

It matters, most of the time the column from the dimension table is used in DAX statement to modify an existing filter context, users who are building their own reports can become confused if they accidentally choose the column from the fact table and the measure (referencing the column from the dimension table) does not behave as expected.

Regards,

Tom