Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Hello everyone,
Starting last week our gen 1 dataflows no longer allow developers to proceed with adding a second data source using the built in new query GUI options. They can add the first source of any type (Oracle, SQL, Teradata, etc.).
If they try to add a second source of any type or even the same type, leveraging our on prem gateway, it won't allow them to click next, whether they have a SQL query or are trying to transform the data using the GUI options.
Does anyone know if the latest service / gateway updates removed any functionality with gen 1 dataflows or if perhaps a bug was introduced?
Solved! Go to Solution.
Hi @CSummers828,
Given the recent instability in Microsoft Fabric, the issue with not being able to add a second data source in Gen1 dataflows is likely tied to a backend bug or service disruption.
As a short-term workaround, you can split each source into separate Gen1 dataflows and use linked entities to combine them. So, we strongly recommend raising a Microsoft support ticket to report the issue and get direct assistance.
To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
For long-term stability, start planning to migrate to Dataflow Gen2, which offers better support for multiple data sources and improved reliability within Microsoft Fabric.
I hope this helped! Feel free to ask any further questions. If this resolved your issue, please mark it as "Accept as Solution" and give us Kudos to assist others.
Thank you.
Hi @CSummers828,
Given the recent instability in Microsoft Fabric, the issue with not being able to add a second data source in Gen1 dataflows is likely tied to a backend bug or service disruption.
As a short-term workaround, you can split each source into separate Gen1 dataflows and use linked entities to combine them. So, we strongly recommend raising a Microsoft support ticket to report the issue and get direct assistance.
To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
For long-term stability, start planning to migrate to Dataflow Gen2, which offers better support for multiple data sources and improved reliability within Microsoft Fabric.
I hope this helped! Feel free to ask any further questions. If this resolved your issue, please mark it as "Accept as Solution" and give us Kudos to assist others.
Thank you.
Hi @CSummers828,
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 for your understanding and assistance.
Hi @CSummers828,
We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?
If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.
Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.
Thank you for your understanding and participation.
@CSummers828 Might be related to all the problems Fabric has been having recently. It's been a nightmare for a lot of people: Fabric practically down : r/MicrosoftFabric