cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Calculate average based on dynamic column reference

Hi all

 

I have source file with following columns: Country, Retailer, Division, Product, 007.2020, 008.2020, 009.2020, 010.2020, 011.2020, 012.2020, 001.2021, Result.

 

I would like to calculate the average over all columns referring to a month (i.e. in above case 007.2020 to 001.2021).

 

However, next time i receive the source file, the months may be different, but they will always be sitting in the same position and there will always be 6 months.

 

I already tried this formula, but get an error:

= Table.AddColumn(#"Pivoted Column", "Average", each List.Average({List.FindText(Table.ColumnNames(#"Pivoted Column"),"202")}), type number)

 

This is the error I get:

Expression.Error: We cannot apply operator - to types List and List.
Details:
Operator=-
Left=[List]
Right=[List]

 

Would anyone know how i could get this to work, in either M or DAX?

 

Thanks!

Bart

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Hello @BartVW 

 

in order to create a dynamically solution, you have to tell us what can be a rule, to select the correct columns. Here an example where I calculated the average of all columns that contain a ".". If this is your requirement, you can use the code, otherwise tell us all names of your columns, and we will find another logic. Replace the source-step and changedtype with your real data table

let
    Source = Table.FromRows(Json.Document(Binary.Decompress(Binary.FromText("i45WMlTSUTICYmMgNgFiUyA2A2JzpdhYAA==", BinaryEncoding.Base64), Compression.Deflate)), let _t = ((type nullable text) meta [Serialized.Text = true]) in type table [Column1 = _t, Column2 = _t, #"007.2020" = _t, #"008.2020" = _t, #"009.2020" = _t, #"010.2020" = _t, Result = _t]),
    #"Changed Type" = Table.TransformColumnTypes(Source,{{"Column1", Int64.Type}, {"Column2", Int64.Type}, {"007.2020", Int64.Type}, {"008.2020", Int64.Type}, {"009.2020", Int64.Type}, {"010.2020", Int64.Type}, {"Result", Int64.Type}}),
    AddAverageOfMonths = Table.AddColumn
    (
        #"Changed Type",
        "AverageMonth",
        (row)=> List.Average(Record.FieldValues(Record.SelectFields(row, List.Select(Table.ColumnNames(#"Changed Type"), each Text.Contains(_,".")))))
    )
in
    AddAverageOfMonths

 

Copy paste this code to the advanced editor in a new blank query to see how the solution works.

If this post helps or solves your problem, please mark it as solution (to help other users find useful content and to acknowledge the work of users that helped you)
Kudoes are nice too

Have fun

Jimmy

 

View solution in original post

5 REPLIES 5

Hi, @BartVW 

Without a glance of your full dataset, I can so far only come up with such suggestions.

  • List.FindText func returns a list, thus no more {} are needed here;
  • Besides, the resulting list is a list of text, it's supposed to be enclosed in Number.From for a conversion before using List.Average.

As far as I'm concerned, I'd usually use DAX to average a list of values within a specific range. But it's not absolute as such; it depends on, more or less, the dataset.

Hi @BartVW ,

 

Try this:

 

Add a custom column like so:

List.Average(List.RemoveLastN(List.RemoveFirstN(Record.FieldValues(_),4),1))

avg.PNG

 

Or, try this:

 

1. UnPivot other columns.

unpivot.gif

 

2. Group.

group.gif

 

3. Expand.

expand.gif

 

4. Pivot.

pivot.gif

 

let
    Source = Table.FromRows(Json.Document(Binary.Decompress(Binary.FromText("i45WcjZU0lEKAhEuICIARJgDsQUQWwKxoQGIAIkaGoEIMA/Ij9UB6gWJBIEIFxARYERArzGQMAICpdhYAA==", BinaryEncoding.Base64), Compression.Deflate)), let _t = ((type nullable text) meta [Serialized.Text = true]) in type table [Country = _t, Retailer = _t, Division = _t, Product = _t, #"007.2020" = _t, #"008.2020" = _t, #"009.2020" = _t, #"010.2020" = _t, #"011.2020" = _t, #"012.2020" = _t, #"001.2021" = _t, Result = _t]),
    #"Changed Type" = Table.TransformColumnTypes(Source,{{"Country", type text}, {"Retailer", type text}, {"Division", type text}, {"Product", type text}, {"007.2020", Int64.Type}, {"008.2020", Int64.Type}, {"009.2020", Int64.Type}, {"010.2020", Int64.Type}, {"011.2020", Int64.Type}, {"012.2020", Int64.Type}, {"001.2021", Int64.Type}, {"Result", Int64.Type}}),
    #"Unpivoted Other Columns" = Table.UnpivotOtherColumns(#"Changed Type", {"Country", "Retailer", "Division", "Product", "Result"}, "Attribute", "Value"),
    #"Grouped Rows" = Table.Group(#"Unpivoted Other Columns", {"Country", "Retailer", "Division", "Product"}, {{"All", each _, type table [Country=nullable text, Retailer=nullable text, Division=nullable text, Product=nullable text, Result=nullable number, Attribute=text, Value=number]}, {"Avg", each List.Average([Value]), type number}}),
    #"Expanded All" = Table.ExpandTableColumn(#"Grouped Rows", "All", {"Attribute", "Value"}, {"Attribute", "Value"}),
    #"Pivoted Column" = Table.Pivot(#"Expanded All", List.Distinct(#"Expanded All"[Attribute]), "Attribute", "Value"),
    #"Reordered Columns" = Table.ReorderColumns(#"Pivoted Column",{"Country", "Retailer", "Division", "Product", "007.2020", "008.2020", "009.2020", "010.2020", "011.2020", "012.2020", "001.2021", "Avg"})
in
    #"Reordered Columns"

 

 

Best Regards,

Icey

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hello @BartVW 

 

in order to create a dynamically solution, you have to tell us what can be a rule, to select the correct columns. Here an example where I calculated the average of all columns that contain a ".". If this is your requirement, you can use the code, otherwise tell us all names of your columns, and we will find another logic. Replace the source-step and changedtype with your real data table

let
    Source = Table.FromRows(Json.Document(Binary.Decompress(Binary.FromText("i45WMlTSUTICYmMgNgFiUyA2A2JzpdhYAA==", BinaryEncoding.Base64), Compression.Deflate)), let _t = ((type nullable text) meta [Serialized.Text = true]) in type table [Column1 = _t, Column2 = _t, #"007.2020" = _t, #"008.2020" = _t, #"009.2020" = _t, #"010.2020" = _t, Result = _t]),
    #"Changed Type" = Table.TransformColumnTypes(Source,{{"Column1", Int64.Type}, {"Column2", Int64.Type}, {"007.2020", Int64.Type}, {"008.2020", Int64.Type}, {"009.2020", Int64.Type}, {"010.2020", Int64.Type}, {"Result", Int64.Type}}),
    AddAverageOfMonths = Table.AddColumn
    (
        #"Changed Type",
        "AverageMonth",
        (row)=> List.Average(Record.FieldValues(Record.SelectFields(row, List.Select(Table.ColumnNames(#"Changed Type"), each Text.Contains(_,".")))))
    )
in
    AddAverageOfMonths

 

Copy paste this code to the advanced editor in a new blank query to see how the solution works.

If this post helps or solves your problem, please mark it as solution (to help other users find useful content and to acknowledge the work of users that helped you)
Kudoes are nice too

Have fun

Jimmy

 

@Jimmy801 thank you, this works great and solves my immediate challenge.

 

As a PQ beginner, i would love to understand more how this works though, and had some questions:

  • what is the "(row) ==> " syntax about? It looks like a function but without 'let' and 'in'?
  • what is the reasoning to go from ColumnNames to List.Select to Record.SelectFields and Record.FieldValues? Why did my original solution not work, just using "each List.Average(List.FindText(Table.ColumnNames(#"Pivoted Column"),"202"))"
  • why do you use the _ variable?

 

Appreciate all the help you can provide, and if you have any good links i could look at for these questions, that would be great too.

 

Cheers

Bart

 

Hello @BartVW 

 

If my answer solved the problem, I would appreciate if you could mark it as solution.

I will shortly try to answer your question, but you could search the documentation for this as well.

- ()=> is the syntax of a function (or each would also work). I could have used also let and in to split my steps, but i prefered to put everything in on line, so no let and in is needed

- columnnames gibs you the headernames, list select filters according your logic (searching for the "." in your header names), Record.Selectfields applies a filter to a row, using the output of list.select as trigger, and Record.Values gives you the values of the rows that where filtered.

- the "_" is needed when you use the each keyword, and represents the input value of this function. (in my case in the the List.Select function and the _ represents a item in the list)

 

 

Hope things are a little more clearer now 🙂

 

If this post helps or solves your problem, please mark it as solution (to help other users find useful content and to acknowledge the work of users that helped you)
Kudoes are nice too

Have fun

Jimmy

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (1,560)