FireFighter1017
Advocate III
1 year agoStatus:
Need Clarification
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.
miguel
Community Admin
1 year agoStatus changed:
New
to Need 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
Add support for identity columns in Fabric warehouses.
Identity columns are a common method for generating surrogate keys in data warehousing scenarios implemented on SQL Server. By adding support for identity columns in Fabric, users could migrate the...dpurdy5 hours agoRegular VisitorCompleted4.4KViews131likes11CommentsFabric UX Idea: Clearly Identify the Source Workspace for Opened Fabric Artifacts
In many Fabric implementations, organizations have multiple projects and environments, for example: Sales Analytics – Development Sales Analytics – UAT Sales Analytics – Production Similarl...Murtaza_Ghafoor11 hours agoSuper UserNew7Views0likes0CommentsCopilot in Power BI should be canvas-aware and support screenshots / direct visual debugging.
Currently, Copilot in Power BI cannot: See the actual canvas / selected visual Accept screenshots or images to aid in troubleshooting Both of these make debugging visual-level issues painful and...dcohare11 hours agoHelper INew10Views1like0Comments