Power bi Semantic model issue

[anonymous0909]

Hi,

I created and published a report in power bi service that created a semantic model, this model is connected to MySQL database, I configured the connected with a gateway and everything seems to be working fine. Then I created a new report connecting to the previous semantic model and then added a different data source, when I published this new report to a different workspace, the data coming from the 1st semantic model is not loading properly. I got this error. Please let me know how to fix and avoid this issue. Thanks

 

[v-pnaroju-msft]

Hi anonymous0909,

We are following up to see if what we shared solved your issue. If you need more support, please reach out to the Microsoft Fabric community.

Thank you.

[v-dineshya]

Hi @anonymous0909 ,

Thank you for reaching out to the Microsoft Community Forum.

Hi @tayloramy  Thank you for your prompt response.

Hi @anonymous0909 ,

The error "A connection could not be made to the data source with the Name of {...}", indicates that the semantic model dataset referenced in your second report is not accessible from the new workspace where you published it. This happens due to cross-workspace dataset access limitations or missing gateway configuration.

Please check below things to fix the issue.

1. Please check that the workspace where the semantic model or original dataset resides has shared access enabled.

Go to original workspace --> dataset --> click on Manage Permissions --> check the target workspace or users have access.

2. If the semantic model is certified, it becomes easier to reuse across workspaces.

Go to original workspace --> dataset → click on Settings --> mark it as Certified or Promoted.

3. In Power BI Admin Portal, check that "Allow users to use datasets across workspaces" is enabled. This is a tenant-level settings and may require admin privileges.

4. Check that the gateway is correctly configured and mapped to the dataset in the original workspace.

Go to Manage Gateways --> check the data source is listed and credentials are valid.

5. In the new workspace, go to the report --> click on Settings --> check the dataset binding. You need to rebind the report to the correct dataset if it’s not automatically linked.

Note: Always publish semantic models to a centralized workspace and certify them for reuse. Use shared datasets instead of duplicating models across workspaces. Maintain a clear gateway mapping and check credentials are up to date. check with your Power BI admin whether the cross-workspace dataset usage is allowed.

I hope this information helps. Please do let us know if you have any further queries.

Regards,

Dinesh

[v-dineshya]

Hi @anonymous0909 ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

Regards,

Dinesh

[v-dineshya]

Hi @anonymous0909 ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

Regards,

Dinesh

[tayloramy · Accepted solution]

Hi @anonymous0909,

That error message shows the report is trying to connect to the upstream semantic model through the Analysis Services endpoint (powerbi://...). Because your new report also added a second source, it became a composite model that DirectQuery-connects to the first semantic model plus another source. When the upstream connection fails at publish/open, it is usually one of four things: missing Build permission on the upstream model, a tenant setting blocking DirectQuery-to-semantic-models, the source model discouraging chaining, or missing credentials/gateway on the added source.

Fix it with this checklist:

1. Grant Build on the upstream semantic model to whoever publishes/owns the new report (and any service principal you use). Without Build, the composite model cannot query the source dataset across workspaces. See composite models permissions and Build permission. For consumers, licensing and permission requirements are also outlined here: permissions update for composite models.
2. Confirm the tenant setting allows DirectQuery to Power BI semantic models. In the Admin portal, turn on Allow DirectQuery connections to Power BI semantic models. If disabled, connections to a published semantic model as a source will fail. Doc: Admin setting.
3. Make sure the source semantic model does not discourage chaining. If the source model was published with the option to discourage DirectQuery connections, new composite connections are blocked. Clear that option and republish the source if needed. Doc: Discourage DirectQuery connections setting.
4. Set credentials/gateway for the added data source in the target workspace. After publishing the new report and its semantic model, go to Manage connections and gateways and configure credentials for the additional source (your original MySQL gateway stays with the first semantic model). Docs: Manage gateway data sources.
5. Republish and test. In Desktop, open the composite model, confirm the connection to the upstream semantic model under Get Data > Power BI semantic models, then Publish. The upstream visuals should now load.

Why the message mentions analysis-services: the upstream semantic model is exposed via the XMLA/Analysis Services endpoint. If Build or the tenant switch is missing, the handshake to that endpoint fails and you see the generic connection error. The docs above cover those prerequisites: composite models, Build permission, and the tenant setting.

If you found this helpful, consider giving some Kudos.
If I answered your question or solved your problem, mark this post as the solution.