Original subtitles

OK so after talking about filter flow in-depth and learning about the risks of using bi directional

filters and the pitfalls of pulling in a foreign key instead of a primary you may be thinking to yourself

Man it is really easy to make major mistakes in power be-I and to some extent that's true without having

a good fundamental knowledge of how data models and filters actually work.

It certainly can be easy to make this type mistake.

But the good news is that power be-I gives us tools to help prevent this type of thing from happening.

For example hiding fields from report view.

Now in either your data view or your relationships you have this option called Hide in report view and

you can simply right click on either a column a field a measure or an entire table and choose this hide

and report view option.

And what that does is essentially make that field or table inaccessible from the report tab that makes

it invisible.

So you can still access the data and see the information within the data or the relationships views

but end users in the report view will not be able to access those fields.

So this is a really common way to prevent users from accidentally filtering using invalid fields like

a foreign key from a data table instead of a primary key from a lookup.

So protip here my recommendation in general is to hide the foreign key columns in your data tables which

will force users to filter using the primary keys from the look.

Since that's the only option they have left.

So let's go ahead back to our Adventure Works demo and work on fool proofing this model.

All right.

So we're back in our Adventure Works report.

We're in the relationships looking at our model and I want to show you how to hide some of these fields.

First of all you can select an entire table right click the header and hide the whole table from report

view which will essentially greyed out.

But we don't want to do that in this case.

We need information from all of our tables including the values or quantities from returns and sales

at least for now.

But what we can do is start hiding some of these foreign keys because 99 percent of the time we don't

want users filtering on dates or products or customers or territories within the data table itself.

You can access that same exact information using fields from the lookup tables instead.

So all we need to do is hover over the field right click and click hide and report you might see it

flash it you like that that's OK.

You can do the same thing for stock date.

There we go.

Grays out.

That means it's now hidden.

We can keep order number in there.

But let's hide product key.

And customer akey and territory key.

There we go.

So all five of those foreign keys the one that connects the customer the two dates that connect the

calendar and the connections to territory and product are now hidden.

We'll do the same thing for returns.

Return Date territory key and product key.

So we haven't lost anything you can easily right click and re-enable any of these fields.

And also note that we could have done the same thing in the Data tab as well.

You'll see we're in our sales data now.

Those columns that we did hired are now greyed out.

You could also select to right click the column header and choose the higher report view option there

as well.

Just two ways to do the exact same thing.

So now here's the real impact.

If we go to the report view here my fields list you'll note that my returns table only has that one

lonely field and my sales table has been chopped down to just these three.

So I remember hiding from report view makes them invisible or inaccessible but only within this one

view.

So there you have it.

That's a great way to fool proof your data model and your power be-I reports by hiding fields from report

you.