Error when exporting a paginated report with effective identity

[desmondpp]

I have a dotnet app that is attempting to export a paginated report using RLS. In the PaginatedReportExportConfiguration, I am setting the Identity Username to a value the report is using to filter the data (the value is a GUID representing the object I want to filter by). This approach works fine when creating an embed token. However, when exporting it gives me an export Id but then the request ultimately fails (the call to get the export status shows that the request is in a failed state). I get no error information from the export status call. How can I find out what is wrong with the export request? 

The docs show that this should work: 

https://docs.microsoft.com/en-us/power-bi/developer/embedded/export-paginated-report#row-level-secur...

{
      "format": "PDF",
      "paginatedReportConfiguration":{
            "identities": [
                  {"username": "john@contoso.com"}
            ]
      }
}

[AmosHersch · Accepted solution]

Hi @desmondpp 

See here: https://docs.microsoft.com/en-us/power-bi/developer/embedded/export-paginated-report#considerations-...

• When exporting a paginated report with an effective identity, the username must be an existing user from your tenant’s Azure Active Directory.

So you cannot provide a GUID, it must be a UPN of a user which exists in your tenant.

[desmondpp]

Ultimately I need to pass a patient identifer to the report to filter the data by patient (where the patient is NOT the user). For the embedded report I stick the patientId in the effective identity username field, which works fine. But when exporting I need to use ParameterValues I guess? That may make it difficult to use the same report for both embedding and exporting. Is there any other way?

[AmosHersch]

I can definately understand your request, and I also think the embedding of the report and the export API should be aligned, but currently the requirement in the API doesn't allow it.

I'm not an expert with pagianted reports, but maybe using report parameters it will be possible to filter the report instead of by username. The export API should work well with parameters.