Is there a field limit when using a pivot in a DataFlow Gen2 flow?

[mklevemann]

Just wondering how many fields you can keep not pivoted when you pivot in a DataFlow Gen2 flow?   

[AntoineW]

Hello @mklevemann,

While there's no documented field limit, performance can degrade if:

• You have many unique values in the pivot key (each becomes a column).
• You keep too many group-by fields, which increases the number of output rows.
• Your dataset is large, and transformations aren't optimized (e.g., no query folding).

Microsoft recommends:

• Keeping pivot transformations focused and minimal.
• Using staging steps or breaking down flows if performance drops.
• Avoiding dynamic schema generation unless necessary. [Pivot tran...rosoft.com]

---

✅ Best Practices

• Specify exact values to pivot (instead of dynamic pivoting).
• Use query folding where possible to push logic to the source.
• Consider using Notebooks or Power BI for complex pivoting if Dataflow Gen2 struggles.

Hope it can help you !

Best regards,

Antoine

[tayloramy · Accepted solution]

Hi @mklevemann, 

There isn’t a documented “field limit” on how many columns you can keep not pivoted in a Dataflow Gen2 pivot step. The real constraints are (a) how many columns your pivot creates overall and (b) the limits of your destination and/or downstream semantic model. In practice, the biggest hard limit you’ll hit is the Power BI semantic model cap of 16,000 columns total across all tables if you load the result into a model later (Microsoft Learn). Power Query’s Pivot itself doesn’t publish a specific column cap (Pivot columns (Power Query)), and Dataflow Gen2’s limitations page doesn’t call out a column-count limit either (Fabric Data Factory limitations).

Why this happens

Pivoting turns each distinct value in your pivot column into a new column. So even if you “keep” many non-pivoted columns, the true risk is the number of new columns created by the pivoted categories. Very wide outputs can hit:

• Semantic model limits: 16,000 total columns across all tables (doc, see “Column limit”).
• Destination practicality: Lakehouse/Delta can handle wide schemas, but extremely wide tables affect performance and manageability (Lakehouse and Delta overview).

Recommendations

• Constrain pivot cardinality: Pre-filter the categories you pivot (e.g., top N, recent period, a whitelist).
• Aggregate smarter: If you’re pivoting for display only, consider leaving the data long and handle layout in the report (measures/visuals) instead of materializing thousands of columns.
• Stage first, pivot later: Land data “long” in Lakehouse, then create a downstream, narrow pivoted table targeted to the use case.
• Sanity check column counts: If the result heads toward thousands of columns, you’re likely to hit usability or model limits later.

If you share your destination (Lakehouse table vs Warehouse vs straight to a semantic model), folks can suggest more targeted guardrails. But to your question: there’s no fixed “keep columns” limit on the Pivot step itself-just be mindful of the resulting total column count and downstream limits.

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

[v-tsaipranay]

Hi @mklevemann ,

Thanks for reaching out to the Microsoft fabric community forum.

Could you please let us know if the issue has been resolved? I wanted to check if you had the opportunity to review the information provided by @AntoineW and  @tayloramy  . If you still require support, please let us know, we are happy to assist you.

Thank you

[mklevemann]

Thanks for the responses.