Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now

Reply
campagna
Regular Visitor

INFO.VIEWS.MEASURES() error when measures are organized in folder and subfolder

Hi all,

 

I'm trying to create a table containing description of all measures in my model to generate a documentation table insiede the report.

 
the INFO.MEASURES() function is not supported when creating a table in the model, instead you need to use INFO.VIEW.MEASURES(). with this function I get the following error Correlation Id: ce45277c-bf50-54e3-8b04-997cdd283b32 Error Details: Failed to move the data reader to the next row. Doing some tests the problem seems to be related to the organization of the measures in folders and subfolders. is this a known issue?
1 ACCEPTED SOLUTION
rajendraongole1
Super User
Super User

Hi @campagna -If feasible, consider using a direct query to your data source to retrieve measure information. This might help bypass some of the limitations present in the Power BI model.As a temporary solution, manually create a documentation table by documenting the measures and their descriptions, especially for critical measures.

You could also use DAX Studio to extract the measure definitions.

 

The INFO.VIEW.MEASURES() function has known limitations in certain scenarios, especially when there are complex hierarchies or an extensive number of measures.

use dax studio and check the below measure:

 

EVALUATE
ADDCOLUMNS(
MEASURES,
"Description", [YourDescriptionMeasure] // Replace with an appropriate measure for description if available
)

 

While the error you’re encountering may relate to measure organization, utilizing workarounds and ensuring your environment is up to date may help mitigate the problem.

 





Did I answer your question? Mark my post as a solution!

Proud to be a Super User!





View solution in original post

1 REPLY 1
rajendraongole1
Super User
Super User

Hi @campagna -If feasible, consider using a direct query to your data source to retrieve measure information. This might help bypass some of the limitations present in the Power BI model.As a temporary solution, manually create a documentation table by documenting the measures and their descriptions, especially for critical measures.

You could also use DAX Studio to extract the measure definitions.

 

The INFO.VIEW.MEASURES() function has known limitations in certain scenarios, especially when there are complex hierarchies or an extensive number of measures.

use dax studio and check the below measure:

 

EVALUATE
ADDCOLUMNS(
MEASURES,
"Description", [YourDescriptionMeasure] // Replace with an appropriate measure for description if available
)

 

While the error you’re encountering may relate to measure organization, utilizing workarounds and ensuring your environment is up to date may help mitigate the problem.

 





Did I answer your question? Mark my post as a solution!

Proud to be a Super User!





Helpful resources

Announcements
New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.

Join our Fabric User Panel

Join our Fabric User Panel

Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.

March Power BI Update Carousel

Power BI Community Update - March 2026

Check out the March 2026 Power BI update to learn about new features.