topic ExportToFileInGroupAsync Fails with 400 Error (Bad Request) in Developer

ExportToFileInGroupAsync Fails with 400 Error (Bad Request)

gah113 — Wed, 28 Sep 2022 19:19:28 GMT

I am building a .NET application to export Power BI reports hosted on an Azure capacity. The following code fails with a 400 Error (Bad Request) without any information:

I have tried making this call manually and the export to PDF works as expected.

Re: ExportToFileInGroupAsync Fails with 400 Error (Bad Request)

AmosHersch — Wed, 28 Sep 2022 19:24:44 GMT

Hi @gah113 ,

Is the report you're exporting a Power BI (PBIX) report or a Paginated (RDL) report?

Assuming it's a PBIX report I suggest yoy try to see the response message body (using fiddler for example) to see if it contains information regarding the error reason.

Re: ExportToFileInGroupAsync Fails with 400 Error (Bad Request)

gah113 — Wed, 28 Sep 2022 21:05:02 GMT

The message body reads: "Export report requires effective identity to be provided for the report's dataset"

I have tried to send the exportRequest with an effectiveIdentity and the same error message is returned.

Note that no effective identity is required when manually sending requests to reports/{reportId}/ExportTo via the REST API.

Re: ExportToFileInGroupAsync Fails with 400 Error (Bad Request)

AmosHersch — Thu, 29 Sep 2022 07:47:30 GMT

AFAIK this error indicates that your report's dataset has RLS applied, so you must provide an effective identity for that dataset in the export request.

Are you sure you've sent the request with effective identity correctly? Did you specify the dataset ID and RLS parameters?

You can try to export a report with a dataset that doesn't have RLS applied and see that you don't get this error.

When you call the API manually you're not using a Service Principal probably, and hence you don't require to provide an effective identity.

Re: ExportToFileInGroupAsync Fails with 400 Error (Bad Request)

gah113 — Thu, 29 Sep 2022 14:39:22 GMT

@AmosHersch thanks for your help! We resolved the issue by specifying a dataset ID in the datasets property of the effective identity we were passing.

Any reason this property is required for Export but not for other calls using effective identity (e.g. GenerateToken)?

Re: ExportToFileInGroupAsync Fails with 400 Error (Bad Request)

AmosHersch — Thu, 29 Sep 2022 14:55:47 GMT

I would expect this property to be required also in GenerateToken request, especially when the request is from a Service Principal. It might work without an effective identity (or without the property) for a master user.