You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's look at the model properties. Click **Model.bim**. In the **Properties** window, you'll see the [model properties](../analysis-services/tabular-models/model-properties-ssas-tabular.md), most important of which is the **DirectQuery Mode** property. This property specifies whether or not the model is deployed in In-Memory mode (Off) or DirectQuery mode (On). For this tutorial, you will author and deploy your model in In-Memory mode.
62
+
Let's look at the model properties. Click **Model.bim**. In the **Properties** window, you'll see the [model properties](../tabular-models/model-properties-ssas-tabular.md), most important of which is the **DirectQuery Mode** property. This property specifies whether or not the model is deployed in In-Memory mode (Off) or DirectQuery mode (On). For this tutorial, you will author and deploy your model in In-Memory mode.
Copy file name to clipboardExpand all lines: docs/analysis-services/tutorial-tabular-1200/supplemental-lesson-configure-reporting-properties-for-power-view-reports.md
+25-25Lines changed: 25 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ manager: kfile
13
13
# Supplemental Lesson - Configure Reporting Properties for Power View Reports
In this supplemental lesson, you will set reporting properties for the AW Internet Sales project. Reporting properties make it easier for end-users to select and display model data in Power View. You will also set properties to hide certain columns and tables, and create new data for use in charts.
16
+
In this supplemental lesson, you will set reporting properties for the AW Internet Sales project. Reporting properties make it easier for users to select and display model data in Power View. You will also set properties to hide certain columns and tables, and create new data for use in charts.
17
17
18
18
Estimated time to complete this lesson: **30 minutes**
19
19
@@ -25,17 +25,17 @@ In order to complete this particular supplemental lesson, you must also have the
25
25
26
26
27
27
## Model properties that affect reporting
28
-
When authoring a tabular model, there are certain properties that you can set on individual columns and tables to enhance the end-user reporting experience in Power View. In addition, you can create additional model data to support data visualization and other features specific to the reporting client. For the sample Adventure Works Internet Sales Model, here are some of the changes you will make:
28
+
When authoring a tabular model, there are certain properties that you can set on individual columns and tables to enhance the user reporting experience in Power View. In addition, you can create additional model data to support data visualization and other features specific to the reporting client. For the sample Adventure Works Internet Sales Model, here are some of the changes you will make:
29
29
30
30
-**Add new data** - Adding new data in a calculated column by using a DAX formula creates date information in a format that is easier to display in charts.
31
31
32
32
-**Hide tables and columns that are not useful to the end user** - The **Hidden** property controls whether tables and table columns are displayed in the reporting client. Items with that are hidden are still part of the model and remain available for queries and calculations.
33
33
34
-
-**Enable one-click tables** - By default, no action occurs if an end-user clicks a table in the field list. To change this behavior so that a click on the table adds the table to the report, you will set Default Field Set on each column that you want to include in the table. This property is set on the table columns that end users will most likely want to use.
34
+
-**Enable one-click tables** - By default, no action occurs if an user clicks a table in the field list. To change this behavior so that a click on the table adds the table to the report, you will set Default Field Set on each column that you want to include in the table. This property is set on the table columns that end users will most likely want to use.
35
35
36
-
-**Set grouping where needed** - The **Keep Unique Rows** property determines if the values in the column should be grouped by values in a different field, such as an identifier field. For columns that contain duplicate values such as Customer Name (for example, multiple customers named John Smith), it is important to group (keep unique rows) on the **Row Identifier** field in order to provide your end users with the correct results.
36
+
-**Set grouping where needed** - The **Keep Unique Rows** property determines if the values in the column should be grouped by values in a different field, such as an identifier field. For columns that contain duplicate values such as Customer Name (for example, multiple customers named John Smith), it is important to group (keep unique rows) on the **Row IDentifier** field in order to provide your end users with the correct results.
37
37
38
-
-**Set data types and data formats** - By default, Power View applies rules based on column data type to determine whether the field can be used as a measure. Because each data visualization in Power View also has rules about where measures and non-measures can be placed, it is important to set the data type in the model, or override the default, to achieve the behavior you want for your end-user.
38
+
-**Set data types and data formats** - By default, Power View applies rules based on column data type to determine whether the field can be used as a measure. Because each data visualization in Power View also has rules about where measures and non-measures can be placed, it is important to set the data type in the model, or override the default, to achieve the behavior you want for your user.
39
39
40
40
-**Set the Sort by Column** property - The **Sort By Column** property specifies if the values in the column should be sorted by values in a different field. For example, on the Month Calendar column that contains the month name, sort by the column Month Number.
41
41
@@ -75,11 +75,11 @@ For detailed information about Default Field Set, see [Configure Default Field S
75
75
76
76
3. In the **Default Field Set** dialog box, in the **Fields in the table** list box, press Ctrl, and select the following fields, and then click **Add**.
4. In the **Default fields, in order** window, use the Move Up and Move Down buttons to put the following order:
81
81
82
-
**Customer Alternate Id**
82
+
**Customer Alternate ID**
83
83
84
84
**First Name**
85
85
@@ -95,7 +95,7 @@ For detailed information about Default Field Set, see [Configure Default Field S
95
95
96
96
7. Finally, perform these same steps for the **Product** table, selecting the following fields and putting them in this order.
97
97
98
-
**Product Alternate Id**, **Product Name**.
98
+
**Product Alternate ID**, **Product Name**.
99
99
100
100
## Table behavior
101
101
By using Table Behavior properties, you can change the default behavior for different visualization types and grouping behavior for tables used in Power View reports. This allows better default placement of identifying information such as names, images, or titles in tile, card, and chart layouts.
@@ -108,7 +108,7 @@ For detailed information about Table Behavior properties, see [Configure Table B
108
108
109
109
2. In the **Properties** window, in the **Table Behavior** property, click **Click to edit**, to open the **Table Behavior** dialog box.
110
110
111
-
3. In the **Table Behavior** dialog box, in the **Row Identifier** dropdown list box, select the **Customer Id** column.
111
+
3. In the **Table Behavior** dialog box, in the **Row IDentifier** dropdown list box, select the **Customer ID** column.
112
112
113
113
4. In the **Keep Unique Rows** list box, select **First Name** and **Last Name**.
114
114
@@ -118,9 +118,9 @@ For detailed information about Table Behavior properties, see [Configure Table B
118
118
119
119
This property setting specifies this column provides a display name to represent row data.
120
120
121
-
6. Repeat these steps for the **Geography** table, selecting the **Geography Id** column as the Row Identifier, and the **City** column in the **Keep Unique Rows** list box. You do not need to set a Default Label for this table.
121
+
6. Repeat these steps for the **Geography** table, selecting the **Geography ID** column as the Row IDentifier, and the **City** column in the **Keep Unique Rows** list box. You do not need to set a Default Label for this table.
122
122
123
-
7. Repeat these steps, for the **Product** table, selecting the **Product Id** column as the Row Identifier, and the **Product Name** column in the **Keep Unique Rows** list box. For **Default Label**, select **Product Alternate Id**.
123
+
7. Repeat these steps, for the **Product** table, selecting the **Product ID** column as the Row IDentifier, and the **Product Name** column in the **Keep Unique Rows** list box. For **Default Label**, select **Product Alternate ID**.
124
124
125
125
## Reporting properties for columns
126
126
There are a number of basic column properties and specific reporting properties on columns you can set to improve the model reporting experience. For example, it may not be necessary for users to see every column in every table. Just as you hid the Product Category and Product Subcategory tables earlier, by using a column's Hidden property, you can hide particular columns from a table that is otherwise shown. Other properties, such as Data Format and Sort by Column, can also affect how column data can appear in reports. You will set some of those on particular columns now. Other columns require no action, and are not shown below.
@@ -131,9 +131,9 @@ You will only set a few different column properties here, but there are many oth
131
131
132
132
1. In the model designer, click the **Customer** table (tab).
133
133
134
-
2. Click on the **Customer Id** column to display the column properties in the **Properties** window.
134
+
2. Click on the **Customer ID** column to display the column properties in the **Properties** window.
135
135
136
-
3. In the **Properties** window, set the **Hidden** property to True. The **Customer Id** column then becomes greyed out in the model designer.
136
+
3. In the **Properties** window, set the **Hidden** property to True. The **Customer ID** column then becomes greyed out in the model designer.
137
137
138
138
4. Repeat these steps, setting the following column and reporting properties for each table specified. Leave all other properties at their default settings.
139
139
@@ -143,13 +143,13 @@ You will only set a few different column properties here, but there are many oth
143
143
144
144
|Column|Property|Value|
145
145
|----------|------------|---------|
146
-
|Geography Id|Hidden|True|
146
+
|Geography ID|Hidden|True|
147
147
|Birth Date|Data Format|Short Date|
148
148
149
149
**Date**
150
150
151
151
> [!NOTE]
152
-
> Because the Date table was selected as the models date table by using the Mark as Date Table setting, in Lesson 7: Mark as Date Table, and the Date column in the Date table as the column to be used as the unique identifier, the Row Identifier property for the Date column will automatically be set to True, and cannot be changed. When using time-intelligence functions in DAX formulas, you must specify a date table. In this model, you created a number of measures using time-intelligence functions to calculate sales data for various periods such as previous and current quarters, and also for use in KPIs. For more information about specifying a date table, see [Specify Mark as Date Table for use with Time Intelligence](../tabular-models/specify-mark-as-date-table-for-use-with-time-intelligence-ssas-tabular.md).
152
+
> Because the Date table was selected as the models date table by using the Mark as Date Table setting, in Lesson 7: Mark as Date Table, and the Date column in the Date table as the column to be used as the unique identifier, the Row IDentifier property for the Date column will automatically be set to True, and cannot be changed. When using time-intelligence functions in DAX formulas, you must specify a date table. In this model, you created a number of measures using time-intelligence functions to calculate sales data for various periods such as previous and current quarters, and also for use in KPIs. For more information about specifying a date table, see [Specify Mark as Date Table for use with Time Intelligence](../tabular-models/specify-mark-as-date-table-for-use-with-time-intelligence-ssas-tabular.md).
153
153
154
154
|Column|Property|Value|
155
155
|----------|------------|---------|
@@ -170,28 +170,28 @@ You will only set a few different column properties here, but there are many oth
Copy file name to clipboardExpand all lines: docs/analysis-services/tutorial-tabular-1200/supplemental-lesson-implement-dynamic-security-by-using-row-filters.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ manager: kfile
13
13
# Supplemental Lesson - Implement Dynamic Security by Using Row Filters
In this supplemental lesson, you will create an additional role that implements dynamic security. Dynamic security provides row-level security based on the user name or login id of the user currently logged on. To learn more, see [Roles](../analysis-services/tabular-models/roles-ssas-tabular.md).
16
+
In this supplemental lesson, you will create an additional role that implements dynamic security. Dynamic security provides row-level security based on the user name or login id of the user currently logged on. To learn more, see [Roles](../tabular-models/roles-ssas-tabular.md).
17
17
18
18
To implement dynamic security, you must add a table to your model containing the Windows user names of those users that can create a connection to the model as a data source and browse model objects and data. The model you create using this tutorial is in the context of Adventure Works Corp.; however, in order to complete this lesson, you must add a table containing users from your own domain. You will not need the passwords for the user names that will be added. To create an EmployeeSecurity table, with a small sample of users from your own domain, you will use the Paste feature, pasting employee data from an Excel spreadsheet. In a real-world scenario, the table containing user names you add to a model would typically use a table from an actual database as a data source; for example, a real DimEmployee table.
19
19
@@ -109,7 +109,7 @@ In this task, you will hide the EmployeeSecurity table, keeping it from appearin
109
109
In this task, you will create a new user role. This role will include a row filter defining which rows of the DimSalesTerritory table are visible to users. The filter is then applied in the one-to-many relationship direction to all other tables related to DimSalesTerritory. You will also apply a simple filter that secures the entire EmployeeSecurity table from being queryable by any user that is a member of the role.
110
110
111
111
> [!NOTE]
112
-
> The Sales Employees by Territory role you create in this lesson restricts members to browse (or query) only sales data for the sales territory to which they belong. If you add a user as a member to the Sales Employees by Territory role that also exists as a member in a role created in [Lesson 11: Create Roles](../analysis-services/lesson-11-create-roles.md), you will get a combination of permissions. When a user is a member of multiple roles, the permissions, and row filters defined for each role are cumulative. That is, the user will have the greater permissions determined by the combination of roles.
112
+
> The Sales Employees by Territory role you create in this lesson restricts members to browse (or query) only sales data for the sales territory to which they belong. If you add a user as a member to the Sales Employees by Territory role that also exists as a member in a role created in [Lesson 11: Create Roles](lesson-11-create-roles.md), you will get a combination of permissions. When a user is a member of multiple roles, the permissions, and row filters defined for each role are cumulative. That is, the user will have the greater permissions determined by the combination of roles.
113
113
114
114
#### To create a Sales Employees by Territory user role
0 commit comments