I'm getting the below error when I upload a PBIX that uses a SQL query (using windows credentials) and a SharePoint Excel file (using OATH credentials). The Excel file provides a parameter to build the SQL query from (idea from https://youtu.be/iiNDq2VrZPY).
I have exhausted by troubleshooting abilities and have no idea what else I could do to resolve this issue. For the record, I'm trying to use my
Personal Gateway as our Enterprise Gateway won't connect to the SharePoint file location. Enterprise Gateway gives the same error
Could you connect to two data source in Power BI Desktop correctly?
Check whether you could drag columns from them into visuals on the report page.
Do you connect to SQL with direct query or import?
When does the error occurs?
when you publish to Power BI Service or when you add data sources under the On-premises gateway?
What did you do for two data source?
Did you use to second(SharePoint Excel file ) to filter the first one(SQL)?
How do you create parameters?
Based on my knowledge, when you create a parameter to connect data from SQL to Power BI, you don't need to create this parameter in another table.
That means in your scenario, you should not create parameter in a SharePoint Excel file.
You should create parameter as this article shows.
I need the ability to change parameters on the fly for my client. The idea that I shared has been the only idea I've seen to give this ability.
SQL was connected through both Import and Direct Query to assist in troubleshooting. The error occurs when published through the On-Premises Gateway.
The Sharepoint file was used to filter the SQL Query, just as shown in the video.
The article you shared will not allow my customers to change parameters as they require to properly view the data.
The linked idea works well when saving the Excel document to a network resource, without the 'Mashup' errors. How do I resolve the 'Mashup' error when connecting to the SharePoint document?