Export to file for paginated report error- integrated security in the connection string

[smile_rainbow]

Hi,

I have created a flow that runs a paginated report and export into excel spreadsheet and saves to one-drive.

Save a paginated report to OneDrive for Business or SharePoint Online - Power BI | Microsoft Docs

But I am getting the below error at 'Export to file for paginated report' stage.

"You have specified integrated security in the connection string for the data source. Please remove it from the connection string and try uploading the report again."

The report is using SQL database and it's running fine on its own but failing in the flow with the above error.

Please can someone help with this.

[srduval]

It is a bug in the API that can't pass through an identity token, I made them aware of the issue when the feature first launched publicly, but they never gave an estimated timeline for fixing it. The only solution I've found so far is to map the report to use a gateway or something other then windows/microsoft authentication. Basically, you have to hardset a username and password in the RDL (or by mapping to a gateway). I'm playing with the raw API with a custom connection to see if I can bypass that security issue, but no luck. 

@AnnaChu is there anything that can be done to resolve the integrated security error?

AnnaChu

[srduval]

@SameerCh 

[smile_rainbow]

Hi @sdruval,

Thanks for your reply.  I am really struggling with this error and raised a ticket with Microsoft but no resolution yet. I am keen to know how did you use the gateway for the report? Also you mentioned about hardsetting a username and password in the RDL. How do you do that?

I look forward to hearing from you as need this working desparately.

Thanks for your help in advance.

[srduval · Accepted solution]

actually just found a new solution to this. under the "manage" menu item (click the vertical ellipse thing)  then manage dataset and uncheck the "Report viewers can only access this data source with their own Power BI identities using DirectQuery." box in the "manage" menu option page. if you are using a SQL authentication, change authentication to be basic, then click sign in otherwise leave it at oauth and click sign in. 

 

[KellyKaye]

Hi @smile_rainbow 

Apologies for the delay in response on your ticket and thank you for your patience.

Can you please send @AnnaChu a direct message, which includes your ticket number, the date submitted and ticket details, so that our team can follow up on with support on the delayed response time? 

Also, @smile_rainbow can you please respond and mark the solution @srduval provided, if it worked for you? 

Thank you also @srduval your solution is spot on! 🙂  @Heddanewman fyi.

Best, 
Kelly Kaye