Power Bi semantic model question

[anonymous0909]

I have a published power bi report with semantic model, the original data source is from MySQL, I created the gateway and everything seems to be working fine with the connection. But I created another report in a different workspace and tried to connect to the other existing semantic model but then when I posted it to power bi service the report was not loading properly. This is the error. I'm not sure what I am doing wrong. Thanks for your help

 

[v-sdhruv]

Hi @anonymous0909 ,
Since we didnt hear back, we would be closing this thread.
If you need any assistance, feel free to reach out by creating a new post.

Thank you for using Microsoft Community Forum

[v-sdhruv]

Hi @anonymous0909 ,

Just wanted to check if you got a chance to review the suggestions provided and whether that helped you resolve your query?

[v-sdhruv]

Hi @anonymous0909 ,

Just wanted to check if you got a chance to review the suggestions provided and whether that helped you resolve your query?

Thank you Super Users for your prompt response to the query.

[GilbertQ]

Hi @anonymous0909 

Are you connecting to your MySQL database using Directquery or import mode? If it is Directquery you have to then connect via the gateway to your Mysql source and cannot go through via another semantic model.

[Poojara_D12 · Accepted solution]

Hi @anonymous0909 

The error you’re seeing indicates that the new report cannot establish a connection to the existing semantic model via the service, even though your MySQL gateway connection works for the original report. This usually happens because when connecting to an existing dataset in another workspace, the new report is using a “Live Connection” to that dataset, and the workspace or dataset permissions are not configured to allow this report to access it. In Power BI, even if a gateway works, a report in a different workspace needs explicit access to the shared dataset: the user publishing the new report must have at least Build permission on the dataset in the original workspace. Without this, the service cannot authenticate the connection to the semantic model, leading to errors that appear like connection failures. Essentially, the issue is permissions and dataset access, not the gateway itself. To fix it, ensure the user publishing the report has Build rights on the target dataset and that the dataset is shared across workspaces correctly.