PowerBI Semantic Models not supported as Direct Query Source in Export to File API

[MicrosoftUser42]

As of now, the Export to File REST API does not support Direct Query Sources (especially PowerBI Semantic Models combined with other data sources). It always shows "Error fetching data for this visual See details" in the final export, even though the report works fine in both PowerBI Desktop and Online.

Took me a full day to figure this out, super annoying as we have already setup all the code for the API exports. Worked well with the reports we tested (that did not use PowerBI Semantic Models and other data sources at once), but not with others. Hope this keeps someone else from going through the same.

[AmosHersch]

I don't think it's true that a report with semantic models with DQ connection to other semantic models cannot be exported using the API.

It might depend on the external data sources (SQL, etc.) of the semantic models. If they are configured with SSO enabled then it might fail to fetch the data from such data sources.

I believe it's more accurate to say that the combination of have DQ to semantic models + having external data sources with SSO enabled is not supported.

[MicrosoftUser42]

Yes, I think you are right. But why is SSO not supported, pretty much everything regarding authentication is managed through SSO at our company. Is there any way to bypass this issue?

[Anonymous]

Hi @MicrosoftUser42 ,

Thanks for your sharing. There are some limitations and considerations when export the report to file, you can find the details in this official documentation.

Best Regards

[MicrosoftUser42]

Thank you for your response! I don't think dynamic binding is the problem, because there aren't multiple semantic models being used as data source. (Would dynamic binding mean, I have to specify the desired semantic model in the API query?)
But I think your hint towards SSO was correct. For the affected report we do use a composite model with data sources that use SSO. I don't think turning SSO off completely would be a good solution, because that is how access to the data is supposed to be managed. But is there any other way to bypass this issue?