Forum Discussion
'The dataflow has never been published.' error when using 'Save as Dataflow Gen2 (CI/CD)' feature
Hi b_vanderlaan
Can you please raise a Microsoft support ticket. You can create a Microsoft support ticket using the link below.
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft LearnIf this helps, then please Accept it as a solution and dropping a "Kudos" so other members can find it more easily.
Hope this works for you!
Thanks.
Hi b_vanderlaan
Yes this feature has been enabled recently into the Fabric.
After creating or modifying your dataflow, ensure you explicitly select the 'Save' or 'Save & run' options. This action should publish the dataflow. However, if 'Save & run' appears unresponsive, try the following steps:
- Open the dataflow ->Make a minor edit (e.g., add and then remove a space in a query) ->Click 'Save' first, then attempt 'Save & run' again.
This approach can sometimes trigger the necessary publishing process.
It's important to note that Dataflow Gen2 with CI/CD and Git support is still in preview and has some limitations. For instance, orchestrating a refresh of such dataflows isn't currently possible in Fabric data pipelines. Additionally, the workspace view doesn't show if a refresh is ongoing for the dataflow. Being aware of these limitations can help set appropriate expectations and guide troubleshooting efforts.
Reference link: Dataflow Gen2 with CI/CD and Git integration - Microsoft Fabric | Microsoft Learn
If the above information helps you, please give us a Kudos and marked the Accept as a solution.
Best Regards,
Community Support Team _ C Srikanth.
Thank you for your response. Yesterday I tried both options ('Save' and 'Save & run') but both did not work. I just attempted your work around:
1. I added a blank query to the dataflow
2. Pressed 'Save', this closed the dataflow
3. Reopened the dataflow and pressed 'Save & run'
4. I received a notification: 'Refresh started', however, after checking 'Recent runs' on the artifact I did not see any changes.
5. I pressed 'Refesh now' on the artifact, I received again the notification 'Refresh started'. This time after checking 'Recent runs' I saw a new run but it indicated the 'DataflowNeverPublishedError' I saw before.
Unfortunately your workaround did not work. I hope you have other suggestions, or can help me troubleshoot.
PS: orchestrating a refresh of such dataflows in Fabric data pipelines has been released this week, I tested it in my workspace and it worked.