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

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
xander2121
Frequent Visitor

Step folding Unknown indicator error behind?

Hello everyone,

 

In the Step foldin indicators there is an "Unknown" indicator which represents absence of query plan due to an error. How do I find out that error? 

1 ACCEPTED SOLUTION
jjgb
Employee
Employee

Hi @xander2121

 

The step indicators are calculated by using the query plan. In "M", the query plan can be obtained by calling Value.Expression(Value.Optimize(...)) on the affected step.

 

For example, a known bug (under investigation) that will produce an "Unknown" step indicator is this:

 

let
  Source = Sql.Database("some_server""some_database", [CreateNavigationProperties = false]),
  Navigation = Source{[Schema = "dbo", Item = "Tags"]}[Data],
  #"Removed top rows" = Table.Skip(Navigation, 4)
in
  #"Removed top rows"

 

I can obtain the error message by adding a new step that obtains the query plan for the affected step:

let
  Source = Sql.Database("some_server""some_database", [CreateNavigationProperties = false]),
  Navigation = Source{[Schema = "dbo", Item = "Tags"]}[Data],
  #"Removed top rows" = Table.Skip(Navigation, 4),
  QueryPlan = Value.Expression(Value.Optimize(#"Removed top rows"))
in
  QueryPlan
 
Hope this helps. If you can, please share your query so we can track this as a bug.
 
Regards,
Jorge

View solution in original post

2 REPLIES 2
jjgb
Employee
Employee

Hi @xander2121

 

The step indicators are calculated by using the query plan. In "M", the query plan can be obtained by calling Value.Expression(Value.Optimize(...)) on the affected step.

 

For example, a known bug (under investigation) that will produce an "Unknown" step indicator is this:

 

let
  Source = Sql.Database("some_server""some_database", [CreateNavigationProperties = false]),
  Navigation = Source{[Schema = "dbo", Item = "Tags"]}[Data],
  #"Removed top rows" = Table.Skip(Navigation, 4)
in
  #"Removed top rows"

 

I can obtain the error message by adding a new step that obtains the query plan for the affected step:

let
  Source = Sql.Database("some_server""some_database", [CreateNavigationProperties = false]),
  Navigation = Source{[Schema = "dbo", Item = "Tags"]}[Data],
  #"Removed top rows" = Table.Skip(Navigation, 4),
  QueryPlan = Value.Expression(Value.Optimize(#"Removed top rows"))
in
  QueryPlan
 
Hope this helps. If you can, please share your query so we can track this as a bug.
 
Regards,
Jorge
v-eqin-msft
Community Support
Community Support

Hi @xander2121 ,

 

Could you please provide some details like when the error occurs and screenshots to help us clarify your scenario?

 

Best Regards,
Eyelyn Qin

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

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

Top Solution Authors
Top Kudoed Authors