Forum Discussion
Error when exporting a paginated report with effective identity
- 4 years ago
Hi desmondpp
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.
Hi desmondpp
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.
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?
- AmosHersch4 years agoMicrosoft Employee
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.