The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi Guys,
regarding this link:
https://datawithdom.com/2024/03/refresh-from-files-without-a-power-bi-gateway/
when i will put my files on sharepoint i do not have to use gateway.
So my workflow is:
1. Create parameter in report and after that create SourceQuery with if statement, if paramEnvironment = "Customer" then Source = SQL.Database else SharePoint.Files (My sharepoint address).
2. When i will set up paramEnvironment to "Customer" and upload this reportto customer tenant on his architecture, what will happen? If he will need to install gateway only for SQL.Database? Or he will need to provide credentials also to sharepoint files within my organization which is the thing which I am trying to avoid so badly...
Can anybody advise? What is the best set up for working with local files and after that publsihing to customer tenant with it's data sources without asking about gateway?
Best,
Jacek
Solved! Go to Solution.
Hi @jaryszek,
Thank you for reaching out in Microsoft Community Forum.
Yes, if you have the SQL.Database source set up for refresh (as shown in your screenshot), it will trigger the required gateway credentials on the customer's end. This is because SQL.Database is an on-premises data source, and Power BI needs a gateway to securely connect to and refresh data from on-premises sources.
1.If the data source is SQL.Database, a gateway is required to perform the refresh.
2.you will need to install the gateway and provide necessary credentials for the database connection.
Please continue using Microsoft Community Forum.
If this post helped to resolve your issue, kindly consider marking it as "Accept as Solution" and give it a 'Kudos' to help others find it more easily.
Regards,
Pavan
Hi @jaryszek,
I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, kindly "Accept as Solution" and give it a 'Kudos' so others can find it easily.
Thank you,
Pavan.
Hi @jaryszek,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please "Accept as Solution" and give a 'Kudos' so other members can easily find it.
Thank you,
Pavan.
Hi @jaryszek,
Thank you for reaching out in Microsoft Community Forum.
Thank you @lbendlin for the helpful response.
As suggested by Ibendlin, I hope this information was helpful. Please let me know if you have any further questions or you'd like to discuss this further. If this answers your question, please "Accept as Solution" and give it a 'Kudos' so others can find it easily.
Please continue using Microsoft community forum.
Regards,
Pavan.
Thank you,
no it is not answering my fundamental questions.
I know the links but I am using whole Customer architecture, i will not have premium capacity but Customer will have amd pay for everything.
Still is not answering my questions above.
Best,
Jacek
Hi @jaryszek,
Thank you for reaching out in Microsoft Community Forum.
Please follow below steps to resolve the error;
1.If you use the SQL.Database data source in the report, the customer will need to install a gateway on their tenant to access the SQL database.
2.For the SharePoint.Files data source, no gateway is required for the customer as SharePoint is a cloud-based service. However, the customer will need to authenticate to SharePoint if the data is not publicly accessible or shared within their environment.
3.When you set the paramEnvironment = "Customer", and switch to the SQL.Database source, only the SQL connection requires a gateway on the customer's end. For SharePoint, no gateway is needed.
Please continue using Microsoft community forum.
If you found this post helpful, please consider marking it as "Accept as Solution" and give it a 'Kudos'. if it was helpful. help other members find it more easily.
Regards,
Pavan.
3.When you set the paramEnvironment = "Customer", and switch to the SQL.Database source, only the SQL connection requires a gateway on the customer's end. For SharePoint, no gateway is needed.
To confirm, if i will have data source set to sharePoint only (customer is not using SQL database source), Customer does not have to install gateway? (no refresh for SQL database?)
Hi @jaryszek,
Thank you for reaching out in Microsoft Community Forum.
Yes, your understanding is correct.If the data source is set to SharePoint only, and you're not using SQL.Database at all, then:
1.The customer does NOT need to install a gateway.
2.Since SharePoint is a cloud source, Power BI Service can connect and refresh data from it without a gateway.
3.The only requirement is that the customer has access to that SharePoint site and has provided appropriate credentials (OAuth) during dataset refresh setup.
Please continue using Microsoft community forum.
If you found this post helpful, please consider marking it as "Accept as Solution" and give it a 'Kudos'. if it was helpful. help other members find it more easily.
Regards,
Pavan.
One more question,
if database SQL source is set up to be refreshed like that:
it will trigger the required gateway credentials ?
Best,
Jacek
Hi @jaryszek,
Thank you for reaching out in Microsoft Community Forum.
Yes, if you have the SQL.Database source set up for refresh (as shown in your screenshot), it will trigger the required gateway credentials on the customer's end. This is because SQL.Database is an on-premises data source, and Power BI needs a gateway to securely connect to and refresh data from on-premises sources.
1.If the data source is SQL.Database, a gateway is required to perform the refresh.
2.you will need to install the gateway and provide necessary credentials for the database connection.
Please continue using Microsoft Community Forum.
If this post helped to resolve your issue, kindly consider marking it as "Accept as Solution" and give it a 'Kudos' to help others find it more easily.
Regards,
Pavan
Is this a multi tenant scenario or is everything contained in a single tenant?
It is a tenant within my Team (my org) for dev purposes and another tenant for each customer...
Might want to consider a mild emebdded solution
Develop scalable multitenancy applications with Power BI embedding - Power BI | Microsoft Learn
Microsoft Fabric - Multi-Tenant Architecture | Microsoft Community Hub
thanks it will be embedded one but paid from customer side.
User | Count |
---|---|
5 | |
5 | |
2 | |
2 | |
2 |
User | Count |
---|---|
10 | |
7 | |
4 | |
4 | |
4 |