Forum Discussion
MongoDB Atlas SQL connection using 2 connections with 1 data gateway problem
Hi Anonymous
I contacted Microsoft support and they were helping me, but finally I managed to find a solution with my colleagues. It turns out that it is possible to create a kind of ‘view’ in a section that Mongo Atlas offers called Data Federation. There I put together both collections, each one from a different cluster and I only needed one connection for both Desktop and Service.
So as this has helped me, I'll give this answer as a solution.
Anyway, thank you very much for the help provided in your comments!
Hi Anonymous, thanks for replying to my problem!
I can see both connections separatedly but in the same gateway and working correctly:
Also in the report semantic model, I can see both connections separated and working too:
The credentials of both connecionts are right because I have been testing using only one connection with both of them and it works without any problem.
Even with all this, still not working.
Hi nbustos,
Since both MongoDB ODBC connections are correctly configured, mapped, and online in your gateway, and the semantic model is detecting and mapping them properly, we can rule out basic credential or mapping issues.
From here, a couple of deeper things to check:
* Check privacy level settings. Even though this is more commonly an issue in Power BI Desktop, the service still enforces data isolation rules. Please verify the privacy levels on both connections in the gateway settings. Go to Manage Gateways > Each connection > Edit credentials. Make sure both have the same privacy level (e.g., Organizational or None). A mismatch here can silently cause issues with data combination.
* Re-publish with reconfigured source (Same DSN). Since you're connecting to two collections from the same MongoDB server, try this as a workaround. In Power BI Desktop, edit the queries so both collections use the same DSN/connection string, and branch off from there. This may mean querying the full database and then filtering by collection/table within Power BI. This helps Power BI treat the data as coming from a single source, avoiding multi-connection schema confusion in the service.
* Make sure your on-premises gateway is running the latest version. An outdated gateway has been known to cause DM_GWPipeline_Gateway_InvalidConnectionCredentials errors with custom connectors or ODBC drivers.
If all of the above are verified and it’s still not resolving, it could be a limitation or bug in how Power BI handles multiple ODBC Mongo connections through the gateway. In that case, I’d recommend raising a support ticket with Microsoft directly.
Please refer below link on how to raise a contact support or support ticket.
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Best Regards,
Hammad.
Hi nbustos,
I wanted to follow up on our previous conversation. Has your issue been resolved or were you able to raise a support ticket with Microsoft Fabric Support?
Your feedback would be greatly appreciated, as it can help us better understand and address similar issues in the community.
Thank you.
Hi Anonymous !
I followed your instructions but it's not working, I will now contact with support team. As soon as they respond me, I will let you know. Thanks for the help!
Hi nbustos ,
Could you please confirm if the issue has been resolved after raising a support case? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.
Thank you.