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

Get certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now

Reply
arkiboys2
Helper III
Helper III

dataflow gen2 applied steps - red mark

hi,

although I see all results I am unable to find out why there is a red mark here

any suggestions how to tackle this? and  should I ignore this since there is result coming back?

in th eexpression below I am trying to remove  ":" if it is present at the beginning or end 

thank you

 

arkiboys2_1-1730538524612.png

arkiboys2_0-1730538696073.png

 

 

1 ACCEPTED SOLUTION
frithjof_v
Community Champion
Community Champion

The red icon you're seeing is a common indicator, indicating that the step won't fold into a source database query. Instead, the step will be processed in the Power Query M engine's memory.

 

The red icon does not indicate that anything will fail. So you don't need to worry about that.

 

However, this icon indicates that this part of the query will not be able to fold. This is about query execution and performance. It is a best practice to keep it green as long as possible (keep as many applied steps as possible green). If possible, consider moving the "Added custom" step to the bottom of your query.


See some useful details here: https://learn.microsoft.com/en-us/power-query/step-folding-indicators

 

It's a good practice to arrange the applied steps so the M query begins with all the steps that fold (the green steps).

 

Typically, we use Choose columns (use Choose Columns or Remove Other Columns instead of Remove Columns, as a best practice) and Filter as our first applied steps. Several other M operations are also able to fold.

 

The ability for M to perform query folding depends on which source system you are using. Typically, SQL-based source systems and relational databases will have good support for query folding of several M operations. For some other sources, M doesn't support query folding or has limited support for it.

 

A good practice is also to split the queries into staging and transformation. For example, you could have one dataflow purely for ingestion (consider using Choose columns and Filters to reduce the amount of data ingested), and another dataflow/stored procedure/notebook/etc. for transformations.

 

As with everything, there is an it depends element here as well. But these are generally considered good practices.

 

Bottom line: the indicator is just there for query execution (query folding) information.

 

For more information, google "Query folding" or "don't break the fold".

View solution in original post

2 REPLIES 2
arkiboys2
Helper III
Helper III

thank you

frithjof_v
Community Champion
Community Champion

The red icon you're seeing is a common indicator, indicating that the step won't fold into a source database query. Instead, the step will be processed in the Power Query M engine's memory.

 

The red icon does not indicate that anything will fail. So you don't need to worry about that.

 

However, this icon indicates that this part of the query will not be able to fold. This is about query execution and performance. It is a best practice to keep it green as long as possible (keep as many applied steps as possible green). If possible, consider moving the "Added custom" step to the bottom of your query.


See some useful details here: https://learn.microsoft.com/en-us/power-query/step-folding-indicators

 

It's a good practice to arrange the applied steps so the M query begins with all the steps that fold (the green steps).

 

Typically, we use Choose columns (use Choose Columns or Remove Other Columns instead of Remove Columns, as a best practice) and Filter as our first applied steps. Several other M operations are also able to fold.

 

The ability for M to perform query folding depends on which source system you are using. Typically, SQL-based source systems and relational databases will have good support for query folding of several M operations. For some other sources, M doesn't support query folding or has limited support for it.

 

A good practice is also to split the queries into staging and transformation. For example, you could have one dataflow purely for ingestion (consider using Choose columns and Filters to reduce the amount of data ingested), and another dataflow/stored procedure/notebook/etc. for transformations.

 

As with everything, there is an it depends element here as well. But these are generally considered good practices.

 

Bottom line: the indicator is just there for query execution (query folding) information.

 

For more information, google "Query folding" or "don't break the fold".

Helpful resources

Announcements
November Carousel

Fabric Community Update - November 2024

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

Live Sessions with Fabric DB

Be one of the first to start using Fabric Databases

Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.

November Update

Fabric Monthly Update - November 2024

Check out the November 2024 Fabric update to learn about new features.

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! Early Bird pricing ends December 9th.