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
- miguel
Community Admin
Status changed:NewtoNeed ClarificationThe 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
Remove the "ownership" and "take over ownership" features for Fabric items
Remove the "ownership" and "take over ownership" features for Fabric items in workspaces. The workspace roles should be the only determinant of who can do what with any Fabric item, following the pri...mike_honey2 hours agoMemorable MemberNew4Views0likes0CommentsAuto Y axis labels and gridlines to be above max value
The operation of the auto y axis labels and gridlines frequently results in charts where the max value is above the maximum visible y axis value. For eg. line charts like the below, where much of the...nicS19814 hours agoNew MemberNew3Views0likes0CommentsDynamic current-period defaults for separate Year and Month slicers
Scenario The target scenario is a report viewed in Power BI Service, using a DirectQuery semantic model and a dedicated Date dimension. Separate Year and Month slicers are part of the required user ...vvargasv2 days agoMicrosoft EmployeeNew13Views0likes0Comments