Skip to content

Commit a0f4cca

Browse files
author
Peer Grønnerup
committed
Added section under impersonation explaining the new option to set customdata property in the connection string.
1 parent f8bbdeb commit a0f4cca

File tree

8 files changed

+281
-12
lines changed

8 files changed

+281
-12
lines changed

content/_apiSource/TOMWrapper.dll

102 KB
Binary file not shown.

content/_apiSource/TOMWrapper.xml

Lines changed: 119 additions & 12 deletions
Large diffs are not rendered by default.
100 KB
Binary file not shown.

content/_apiSource/TabularEditor3.Shared.xml

Lines changed: 145 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
5.92 KB
Loading
5.12 KB
Loading
14.2 KB
Loading

content/onboarding/refresh-preview-query.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -135,6 +135,23 @@ Once the impersonation is enabled, the **Impersonation..** button is checked, an
135135

136136
When auto-refresh is enabled on a data view, changing the impersonation will immediately refresh the view.
137137

138+
## CustomData
139+
140+
The CustomData feature allows you to pass a custom string value that can be used in DAX expressions, typically for implementing dynamic row-level security scenarios. This feature can be combined with any of the impersonation options described above, including **No Impersonation**.
141+
142+
![Select Impersonation](~/content/assets/images/impersonation-customdata.png)
143+
144+
When you enter a value in the **CustomData** input field, Tabular Editor 3 adds the [`CustomData` property](https://docs.microsoft.com/en-us/analysis-services/instances/connection-string-properties-analysis-services?view=asallproducts-allversions#customdata) to the connection string. This value can then be retrieved within your DAX expressions using the [`CUSTOMDATA()` function](https://dax.guide/customdata/).
145+
146+
CustomData is commonly used in implementing dynamic row-level security when an application uses custom authentication. The value you provide can be leveraged in role filter expressions to control which rows users can see based on the custom data passed through the connection string.
147+
148+
This feature is particularly useful in **Power BI Embedded** scenarios, where you can natively utilize CustomData to add row filters that pass free text (strings) to leverage dynamic row-level security in embedded reports, dashboards, and tiles.
149+
150+
**Example use case:** You might pass a user's department or region as CustomData, and then use that value in a role's filter expression like:
151+
```dax
152+
'Department'[DepartmentCode] = CUSTOMDATA()
153+
```
154+
138155
# VertiPaq Analyzer
139156

140157
Tabular Editor 3 includes a version of the open-source [VertiPaq Analyzer](https://www.sqlbi.com/tools/vertipaq-analyzer/) tool, created by [SQLBI](https://sqlbi.com). VertiPaq Analyzer is useful to analyze VertiPaq storage structures for your Power BI or Tabular data model.

0 commit comments

Comments
 (0)