Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Sign up nowGet Fabric certified for FREE! Don't miss your chance! Learn more
I'm a workspace admin across all our workspaces. One of our pro users tried creating a report from pre-existing semantic models in the service. Creating the report worked fine in desktop and even worked for a bit after publishing to a test workspace. He was waiting for me to come in and help him move the report to production workspace when he noticed that the gateway connections were now lost. This isn't our traditional way of doing things in the shop and this pro user is sort of a test case on re-using semantic models already published to service. We have been going back and forth with Microsoft on using their lakehouse and warehouse capabilities but some of the functional limitations of live connections have been preventing us from doing so. I was under the impression that gateway settings for this particular report shouldn't matter since it's using semantic models that have already been configured for data source.
Can anyone shed more light on this user's issues? Thank you.
Below is what the pro user sees on his end -
This is what I see on my end when going to semantic model settings for the particular report this user was trying to create from pre-existing models.
Solved! Go to Solution.
Hi @pborah,
Thank you @sergej_og for the prompt response.
Thank you for the details, here the issue is because when the new dataset created from desktop it still contains underlying data sources, so the service needs those sources to be mapped to a gateway again.
Please go to the dataset --> Settings --> Gateway and connections, select the enterprise gateway, and use the
Maps to: dropdown and map it to the correct gateway data source or cloud connection.
Once these mappings are applied the dataset will resolve all connections and the report will work normally.
Thanks and regards,
Anjan Kumar Chippa
Hi @pborah,
Thank you @sergej_og for the prompt response.
Thank you for the details, here the issue is because when the new dataset created from desktop it still contains underlying data sources, so the service needs those sources to be mapped to a gateway again.
Please go to the dataset --> Settings --> Gateway and connections, select the enterprise gateway, and use the
Maps to: dropdown and map it to the correct gateway data source or cloud connection.
Once these mappings are applied the dataset will resolve all connections and the report will work normally.
Thanks and regards,
Anjan Kumar Chippa
Hi @pborah,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution I have provided for the issue user worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa
Hi @pborah,
We wanted to kindly follow up to check if the solution I have provided for the issue user worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa
Hey @pborah ,
what is going to happen if you apply the according "Map to:" setting from the dropdown (Cloud connections)?
Strange behaviour with this one.
Never saw something before for the underlying dataset.
Regards
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 19 | |
| 10 | |
| 8 | |
| 7 | |
| 7 |
| User | Count |
|---|---|
| 51 | |
| 44 | |
| 30 | |
| 27 | |
| 25 |