Forum Discussion
Data Source Not Populating Visuals Even Though Successfully Connected?
Discovered the reason why my report was not publishing!
Desktop loaded one of my SQL queries as a Direct Query and not an Import.
This is a small data table so import mode made sense.
When I reconnected the two tables via Import Mode it published with no issues.
I hope this helps anyone who comes across this problem!
I've tried all options except for the last one. I don't have access to update the Gateway unfortunately. But it's also weird because all my data connections work on Desktop.
And I use the same data connections for 2 other reports that successflly published...... But this one (using the same data source) will not publish???
When I publish this report from Desktop I get a 'Success' notification that it was published, but then after none of the visuals load once on the gateway I get a "The report couldn't access the data source." Despite the fact that there are no errors under the Semantic Model-->Settings--> Data Connections or Credentials.
And the report refreshed fine in Desktop....
Hi CracktheCode85 ,
Thank you for your response.
Even if the connection looks identical in Desktop and you have used the same source in other reports, Power BI treats each data source string as distinct, so even a difference in casing or an extra space can prevent a proper match.
- Open one of the working PBIX files.
- Go to Advanced Editor in Power Query.
- Copy the exact connection string and structure.
- Paste/replicate that structure into the problematic report’s queries.
This ensures both reports use byte-identical connection strings, which will allow the Gateway to match them.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thank you!!
Thank you for the help troubleshooting. Unfortunately I still get the same error using a known working query that is published to another report.
So not sure what is going on here- but I'll be escalating this to our IT team for further assistance.
Thank you!Hi CracktheCode85 ,
Thank you for your response!!
If any of the responses helped resolve the issue or guided you toward the resolution, kindly consider marking it as the accepted solution. This helps others in the community who may face a similar problem.
Thank you!