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

Get inspired! Check out the entries from the Power BI DataViz World Championships preliminary rounds and give kudos to your favorites. View the vizzies.

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
Microsoft Employee
Microsoft 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
Microsoft Employee
Microsoft 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
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!

FebPBI_Carousel

Power BI Monthly Update - February 2025

Check out the February 2025 Power BI update to learn about new features.

March2025 Carousel

Fabric Community Update - March 2025

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

Top Solution Authors