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

Be one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now

Reply
campagna
New Member

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
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

November Carousel

Fabric Community Update - November 2024

Find out what's new and trending in the Fabric Community.

Dec Fabric Community Survey

We want your feedback!

Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.