Export to JSON feature for Dataflow Gen2
How are we supposed to do version control if there is no option to export to JSON like we had with Gen1?
I don't want to commit changes using git integration.
1 Comment
- miguelCommunity AdminStatus changed:NewtoNeed Clarification
The GIT approach is our suggested approach when version control is required. GIT brings a number of capabilities that do fit perfectly with the task of handling version control.
Would you mind sharing more about what sort of scenarios or challenges you're facing today that cannot be addressed with git? Or perhaps what scenarios could only be addressed by having a JSON export of the Dataflow definition?
Please do bare in mind that you can also leverage the REST API today to get the full Dataflow definition without ever setting up GIT for your workspace:
https://learn.microsoft.com/en-us/rest/api/fabric/dataflow/items/get-dataflow-definition
Recent ideas
Data Pipelines - Run only selected activities
For debugging and testing pipeline activities during development, allow us to select one or multiple activities and run only the selected pipeline activities. For example, I'm working on editing ...frithjof_v17 hours agoCommunity ChampionNew618Views11likes2CommentsSemantic model connection bindings should be in source control (Git)
Semantic model data source connection bindings should be source controlled. A semantic model can contain multiple data source references, each of which can be mapped to a separate Fabric data connec...frithjof_v1 day agoCommunity ChampionNew20Views1like0CommentsBulk changing column names in Visualizations Pane
We often use raw/api column names or measures with a set nomenclature to be consistent and to keep track of them but we do not want to display these names in the visuals. Currently we have to change ...vishal1401971 day agoFrequent VisitorNew6Views0likes0Comments