Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:00,900 --> 00:00:07,740
OK so after talking about filter flow in-depth and learning about the risks of using bi directional
2
00:00:07,740 --> 00:00:14,220
filters and the pitfalls of pulling in a foreign key instead of a primary you may be thinking to yourself
3
00:00:14,430 --> 00:00:22,300
Man it is really easy to make major mistakes in power be-I and to some extent that's true without having
4
00:00:22,300 --> 00:00:27,150
a good fundamental knowledge of how data models and filters actually work.
5
00:00:27,150 --> 00:00:30,340
It certainly can be easy to make this type mistake.
6
00:00:30,510 --> 00:00:35,900
But the good news is that power be-I gives us tools to help prevent this type of thing from happening.
7
00:00:36,090 --> 00:00:39,220
For example hiding fields from report view.
8
00:00:39,540 --> 00:00:46,680
Now in either your data view or your relationships you have this option called Hide in report view and
9
00:00:46,680 --> 00:00:54,000
you can simply right click on either a column a field a measure or an entire table and choose this hide
10
00:00:54,000 --> 00:00:55,640
and report view option.
11
00:00:55,830 --> 00:01:02,400
And what that does is essentially make that field or table inaccessible from the report tab that makes
12
00:01:02,400 --> 00:01:03,620
it invisible.
13
00:01:03,750 --> 00:01:09,590
So you can still access the data and see the information within the data or the relationships views
14
00:01:10,200 --> 00:01:15,560
but end users in the report view will not be able to access those fields.
15
00:01:15,570 --> 00:01:22,320
So this is a really common way to prevent users from accidentally filtering using invalid fields like
16
00:01:22,320 --> 00:01:27,030
a foreign key from a data table instead of a primary key from a lookup.
17
00:01:27,060 --> 00:01:34,470
So protip here my recommendation in general is to hide the foreign key columns in your data tables which
18
00:01:34,470 --> 00:01:38,980
will force users to filter using the primary keys from the look.
19
00:01:39,090 --> 00:01:41,880
Since that's the only option they have left.
20
00:01:42,000 --> 00:01:47,270
So let's go ahead back to our Adventure Works demo and work on fool proofing this model.
21
00:01:48,480 --> 00:01:48,900
All right.
22
00:01:48,900 --> 00:01:51,310
So we're back in our Adventure Works report.
23
00:01:51,450 --> 00:01:56,560
We're in the relationships looking at our model and I want to show you how to hide some of these fields.
24
00:01:56,940 --> 00:02:02,490
First of all you can select an entire table right click the header and hide the whole table from report
25
00:02:02,490 --> 00:02:04,880
view which will essentially greyed out.
26
00:02:05,100 --> 00:02:06,780
But we don't want to do that in this case.
27
00:02:06,780 --> 00:02:13,350
We need information from all of our tables including the values or quantities from returns and sales
28
00:02:13,440 --> 00:02:14,610
at least for now.
29
00:02:14,970 --> 00:02:21,780
But what we can do is start hiding some of these foreign keys because 99 percent of the time we don't
30
00:02:21,780 --> 00:02:29,020
want users filtering on dates or products or customers or territories within the data table itself.
31
00:02:29,100 --> 00:02:34,810
You can access that same exact information using fields from the lookup tables instead.
32
00:02:35,130 --> 00:02:42,300
So all we need to do is hover over the field right click and click hide and report you might see it
33
00:02:42,300 --> 00:02:44,500
flash it you like that that's OK.
34
00:02:44,580 --> 00:02:47,500
You can do the same thing for stock date.
35
00:02:47,510 --> 00:02:48,000
There we go.
36
00:02:48,010 --> 00:02:48,630
Grays out.
37
00:02:48,630 --> 00:02:50,470
That means it's now hidden.
38
00:02:50,470 --> 00:02:52,370
We can keep order number in there.
39
00:02:52,810 --> 00:02:54,620
But let's hide product key.
40
00:02:55,880 --> 00:03:01,040
And customer akey and territory key.
41
00:03:01,150 --> 00:03:01,550
There we go.
42
00:03:01,550 --> 00:03:07,040
So all five of those foreign keys the one that connects the customer the two dates that connect the
43
00:03:07,040 --> 00:03:11,640
calendar and the connections to territory and product are now hidden.
44
00:03:11,680 --> 00:03:13,960
We'll do the same thing for returns.
45
00:03:14,060 --> 00:03:19,380
Return Date territory key and product key.
46
00:03:19,840 --> 00:03:24,870
So we haven't lost anything you can easily right click and re-enable any of these fields.
47
00:03:24,970 --> 00:03:28,570
And also note that we could have done the same thing in the Data tab as well.
48
00:03:28,600 --> 00:03:30,780
You'll see we're in our sales data now.
49
00:03:31,090 --> 00:03:33,900
Those columns that we did hired are now greyed out.
50
00:03:34,210 --> 00:03:39,550
You could also select to right click the column header and choose the higher report view option there
51
00:03:39,550 --> 00:03:40,500
as well.
52
00:03:40,540 --> 00:03:43,140
Just two ways to do the exact same thing.
53
00:03:43,150 --> 00:03:45,390
So now here's the real impact.
54
00:03:45,520 --> 00:03:52,840
If we go to the report view here my fields list you'll note that my returns table only has that one
55
00:03:52,840 --> 00:03:57,580
lonely field and my sales table has been chopped down to just these three.
56
00:03:57,940 --> 00:04:05,080
So I remember hiding from report view makes them invisible or inaccessible but only within this one
57
00:04:05,080 --> 00:04:05,840
view.
58
00:04:06,220 --> 00:04:07,430
So there you have it.
59
00:04:07,450 --> 00:04:13,840
That's a great way to fool proof your data model and your power be-I reports by hiding fields from report
60
00:04:13,900 --> 00:04:14,140
you.
6060
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.