Forum Discussion
Post PatronExport to file for paginated report error- integrated security in the connection string
Try changing the datasource settings and unchecking 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.
The problem is with the pagainted report. The API is unable to authenticate the export using windows or microsoft account authentication. It appears to need to be mapped to a gateway or SQL authentication.
Anonymous is there anything you can do to get a resolution to this? passing a value through the identities placeholder doesn't work either. I still get the same error
Post Patronhi @sdruval,
I am using SQL authentication but still not working.
Try changing the datasource settings and unchecking 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.
- bml123
Hi sdruval,
Thank you so much for this. You made my day.
It's working now. Just can't believe that simple untick makes it working.
How did you know this? Thanks alot for this information.
Thank you very much. It saved us lot of time with this working again.
Just happened to stumble upon it. I've been trying to figure out why it's been doing this intermittently for awhile now, and never thought to look at the datasource settings until now. I have no idea why this isn't published in any of the microsoft documentation about using the API for either custom connection or the action item they provide.
I'll have to try it on my end and see what happens. I know the only time i've gotten this to work is if I assign the report to use a gateway. When it uses the gateway it runs as SQL authentication, so I just assumed SQL Auth in the actuall connection string would work.