eMobileBI wrote:
However, the embed only works for the customer whose SQL server was originally hardcoded into the PBIX file. For everyone else, I get "See details" and the XHR JSON for querydata shows:
...{"Id":"DS0","odata.error":{"code":"QuerySystemE
rror","source":"PowerBI","message":{"lang":"en-US" ,"value":"Failed to execute the DAX query."}...
Instead of hardcoding the Azure hostname, I also tried using a query parameter and I get the same results.
1) Is there a way to change the query parameter (which contains the SQL server hostname) either during import PBIX via command-line or when embedding it on to a webpage?
2) It is even possible to change the SQL server hostname used by all the tables in a PBIX file via REST API (i.e. without using PowerBI Desktop)?
3) If I have 100 customers and each of them needs the exact same PBIX but pointing to their own SQL server, do I need 100 copies of the PBIX file with the query parameter set to each customer's SQL server? This seems insane to maintain but after hours of searching online, I'm beginning to feel there is no alternative.
Supposing you're talking about the Power BI service, not Power BI Embedded.
What do you mean "hardcoded"? I don't quite get this. AFAIK, I think it is not possible to use one report but pointing to the indivisual datasource according to Who's viewing it in Power BI Service.
For maintainance flexibility, you can develop/update one pbix and import it to Power BI Serivce. I guess you may use Group to isolate the customers? so import one pbix to indivisual groups and update connection string and credential accordingly, all in a programmatical way.
For Power BI Embedded, you can try to update the connection string and credential every time according to the viewer before they view the report. It looks promising as you can have only one report, however I would have concern about the performance.
Check update connection string in Power BI Embedded.
All in all, IMHO, the most reasonable way is using Row Level Security, you can gather all the data in one place and use one pbix. People would only see what they're allowed to see. However it seems that you're trapped by regulatory/legal reasons.