Forum Discussion
Df gen2 Save Changes deficiency
A major diffrence between gen1 and gen2 is while exiting the gen1 df it gives the following options
Gen 1
at exit
at bottom
vs Gen2
at exit
at bottom
The implication of the above is,
if I open the same gen1 df in two different browser tabs and edit and save one (tabl1 -v1 to v2) and then I can simply exit out of the other dataflow in other browser tab (tab2 - v1) by choosing any of the options (at exit, at bottom). The current datatflow is v2 (desired v2).
but for gen2 df
if I open the same gen2 df in two different browser tabs and edit and save one (tabl1 - v1 to v2) and then if I exit out of the other dataflow in other browser tab (tab2 - v1) because it neither gives Save/Dsicard/Cancel option at exit nor the Cancel option at bottom, v2 gets overwritten by v1. The current datatflow is v1 (desired v2).
It means one would be heavily penalized if unaware of this behavior and can loose hours of work.
Can you please test this on your side and let me know if a permanent fix is expected? This has undesirable effects.
answering further on this smpa01
Dataflow Gen2 with CI/CD has a behavior that matches your expectation. When you exit without clicking the "save" button, you are prompted with a new dialog to "Discard", "Save" or "Cancel". Screenshot of this dialog below:
Answering the question around REST API support, Dataflow Gen2 with CI/CD support now has endpoints through the Fabric REST API. You can use either the Dataflow endpoints:
Items - REST API (Dataflow) | Microsoft Learn
Or use the Fabric core endpoints:
Items - REST API (Core) | Microsoft Learn
As mentioned before, Dataflow Gen2 doesn't have REST API support. Power BI Dataflows (also known as Gen1 Dataflows) do have REST API support and its generally available.
Adding to the experience, Dataflow Gen2 with CI/CD support also has Multitasking support so you could have multiple Dataflows open at the same time if needed
We plan to go GA with Dataflow Gen2 with CI/CD support really soon, so I'd encourage you to perform any comparisons against Dataflow Gen2 with CI/CD support.
11 Replies
Would you mind trying to use Dataflows Gen2 with CI/CD support and share your feedback on the experience available in it?
More info about it below:
https://learn.microsoft.com/en-us/fabric/data-factory/dataflow-gen2-cicd-and-git-integration
Since DF Gen2 CICD is in preview, I can't use this PROD and also it does not show up in API Reponse. I do advanced workflow orchestration and GEN2 CICD does not serves that purposes.
Besides, I have full scale solution developed based on datamart (preview) and it is going to be withdrawn now. I still have to devise a solution for that for a non-fabric client with datamart currently in full-blown PROD. So i learnt my lesson (even if it had not API issue) not to develop with preview elements.
So
either
please fix the weakness as I mentioned in current gen2 df (non-ciccd)
or
make gen2 cicd (GA) that also shows up in api reponse
Feedback received. I've shared it with my internal team.
I would still highly encourage you to explore the Dataflow Gen2 with CICD support as we have every intent to GA that experience.
Hi smpa01 ,
I understand the frustration when things don't work as expected. Thank you for your patience and for providing such detailed information, which truly helps the community understand the challenge better. The platform is continuously evolving, and the team is aware of this gap. With ongoing feedback, we hope to see improved support for service principals and more comprehensive CI/CD integration soon.
From what I’ve seen and based on the miguel response earlier, it appears that SPN authentication is not currently supported in Web activities within Fabric pipelines. Additionally, Dataflow Gen2 (CI/CD) support in pipelines is still in preview and is not yet fully integrated as a pipeline activity.
Thank you miguel , for your valuable information.
Regards,
Yugandhar.
smpa01 Dataflow Gen2 with CI/CD is now Generally available. SPN support was rolling out during the past few days, but it is now available as well and is reflected in the documentation as well.
Below is the blog that talks more about this release:
Do let us know if you have any other questions or feedback.
