dataflows-save-as-authoring-cli

Assess Gen1 dataflow readiness and create Gen2.1 copies via Power BI and Fabric REST APIs.

3|6|Updated Jun 21, 2024
One-click install
npx skills add https://github.com/rritec/Microsoft-Fabric --skill dataflows-save-as-authoring-cli-rritec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dataflows-save-as-authoring-cli
Source: https://github.com/rritec/Microsoft-Fabric/tree/main/skills/plugins/fabric-authoring/skills/dataflows-save-as-authoring-cli
Command: npx skills add https://github.com/rritec/Microsoft-Fabric --skill dataflows-save-as-authoring-cli-rritec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you find Gen1 Microsoft Fabric and Power BI dataflows, determine whether they are safe to upgrade, and create Gen2.1 save-as copies without breaking downstream processes.

Core Features & Use Cases

  • Discovery and readiness assessment: Scan a workspace or tenant for Gen1 dataflows and evaluate seven risk signals such as BYOSA storage, DirectQuery, linked entities, and ownership issues.
  • Guarded save-as execution: Run the native save-as flow to create upgraded Gen2.1 copies while preserving the original Gen1 dataflow.
  • Post-migration validation: Verify artifact state, review non-fatal warnings, and check for residual Gen1 dependencies after the copy is created.
  • Use case: A Fabric admin wants to migrate several legacy dataflows from a workspace, identify blockers first, and then create upgraded copies only for the approved items.

Quick Start

Ask the assistant to scan the target workspace for Gen1 dataflows, assess readiness, and create a Gen2.1 save-as copy for any approved item.

Frequently Asked Questions about dataflows-save-as-authoring-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Power BI dataflows to Microsoft Fabric without breaking downstream processes?

You can migrate Power BI dataflows by scanning your workspace for Gen1 items, assessing readiness using seven risk signals like BYOSA storage and linked entities, and executing a guarded save-as flow to create Gen2.1 copies while preserving the originals.

What are the blockers for upgrading Gen1 dataflows in Microsoft Fabric?

Common blockers for upgrading Gen1 dataflows include BYOSA storage configurations, DirectQuery connections, linked entities, and ownership issues. The readiness assessment evaluates these seven risk signals before attempting a save-as upgrade.

How do I check if a dataflow is ready for a save-as upgrade using REST APIs?

You can check dataflow upgrade readiness by calling Power BI and Fabric REST APIs to scan the tenant or workspace, classifying risk signals, and verifying ownership before executing the saveAsNativeArtifact operation.

Does the dataflow save-as migration process validate the new Gen2.1 copy?

Yes, post-migration validation verifies the artifact state, reviews non-fatal warnings, and checks for any residual Gen1 dependencies after the Gen2.1 save-as copy is created to ensure migration success.

What is the safest way to create Gen2.1 dataflow copies in Microsoft Fabric?

The safest way to create Gen2.1 dataflow copies is through a guarded save-as execution that runs the native save-as flow after a full readiness assessment, ensuring the original Gen1 dataflow remains intact and unbroken.

Can I assess dataflow migration readiness across an entire Fabric tenant?

Yes, you can assess dataflow migration readiness across an entire Fabric tenant by running a tenant-level scan that evaluates all Gen1 dataflows for risk signals and ownership issues before approving any save-as operations.