I've been pulling my hair out over this the last couple of days so decided to reach out the community incase there's something I'm missing or whethers it's just a bug.
I have a basic flow:
Power BI: On Power BI button click
SQL: Execute stored procedure
Excel Online (Business): List rows present in a table
For each record - SQL: Insert rows
Power BI: Refresh a dataset
In short, on triggering, truncates a SQL table, reads an excel workbook on sharepoint being used to collect some data, inserts that data into the previously truncated table. Refreshes a Power BI dataset (contains the SQL table mentioned).
Connections Used for Run Only users.
Connections used list below:
My issues are two fold:
Some users are able to run this flow from the Power BI trigger, and others cannot. All users are included in the run only list, all users have access to the SQL database, workbook on sharepoint, Power BI report and underlying semantic model. I've even checked licenses in O365, which are identical for all users. There is no obvious reason why some users can run it and others cannot.
The second, but possibly related issue, is that I have a near identical flow for another report. The only difference is it's a different Power BI report and different table, but stored on the same database. The sharepoint file is the same, just a different table in the same workbook. In this case all users can run it. So it's not clear why some users can run this flow, but not the one mentioned above, nor is it clear why some users can't run it full stop. I've tried duplcating the original flow that all users can run and just changing which SQL table it's pointed at and Sharepoint table within the same workbook - still doesn't work for some users. I've also tried recreating the flow from scratch, with the same outcome.
