Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
I've created an Azure DevOps query that contains 40 columns. I then created a Power BI report that connects to this query using the "Open in Power BI" export option found in the DevOps query. It's been refreshing and running fine for a couple months.
I recently went to add a new column to the DevOps query I needed, which brings it to 41 columns. When I go to update the Power BI file with a new column and refresh the dataset the new column comes in as expected.
However, there are two columns that no longer refresh any longer and come in with blank data: Node Name and Parent. As soon as I remove that 41st column and refresh the dataset all is coming back again as expected (minus the new column, of course). It doesn't matter which new column I add.
Is there some type of limit to 40 columns between Azure DevOps and Power BI?
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 48 | |
| 45 | |
| 41 | |
| 20 | |
| 17 |
| User | Count |
|---|---|
| 69 | |
| 64 | |
| 32 | |
| 31 | |
| 27 |