Forum Discussion
Embed a paginated report with RLS and CUSTOMDATA dataset shows error regarding CSDL.
- 3 years ago
I solved the puzzle. The thing is, if you want to use paginated reports, the dataset can't use RLS. Instead, to achieve RLS-like behavior, you should use the username attribute in the embedToken request and the built-in field 'User!ID' in the report builder expression.
Here's an example of an 'embedToken' request:
Endpoint: https://api.powerbi.com/v1.0/myorg/GenerateToken
{ "datasets": [ { "id": "dataset_with_no_rls_id", "xmlaPermissions": "ReadOnly" } ], "reports": [ { "id": "report_connected_to_dataset_id" } ], "identities": [ { "username": "constraint_value", "reports": [ "report_connected_to_dataset_id" ] } ] }Also, it's important to note that in order to use this approach, you must connect to the dataset using the XMLA endpoint. Otherwise, it won't work.
Could you confirm if the paginated report was created in PowerBI Report Builder, or in the web portal authoring experience? Exportable Formatted Data Tables (Preview) | Microsoft Power BI Blog | Microsoft Power BI
First, thanks for your response. And yes, It was created on the web portal.
- onepowerbiguy3 years agoFrequent Visitor
After your question, I created a paginated report using Report Builder and error has gone! Thanks for that. Paginated report loads now, but the thing is, customdata is not applied.
CUSTOMDATA still not filtering my data in the paginated report (role_by_category has a very simple rls condition):
[Category] = CUSTOMDATA()If I run a Power BI Report, CUSTOMDATA works as expected (showing just category_1). But I can't replicate that behaiour in the paginated version.
Thanks!