cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
MichalHoltz Frequent Visitor
Frequent Visitor

How to do an average of multiple columns?

I have 3 columns and would like to get the average of 3 of them. How do I do that?

App1App2App3
121
321
235
345
543
254
1 ACCEPTED SOLUTION

Accepted Solutions
Super User
Super User

Re: How to do an average of multiple columns?

@MichalHoltz you right!

 

what about 

 

(AVERAGE(Table2[SAP SRM Functionality])+average(Table2[SAP SRM Productivity])+average(Table2[SAP SRM Quality])+average(Table2[SAP SRM Support]))/4?

 

 


Did I answer your question? Mark my post as a solution.
Proud a to be a Datanaut!
6 REPLIES 6
Super User
Super User

Re: How to do an average of multiple columns?

@MichalHoltz

 

create a measure;

 

measure = average(sum(col1) + sum(col2) +sum(col3))


Did I answer your question? Mark my post as a solution.
Proud a to be a Datanaut!
MichalHoltz Frequent Visitor
Frequent Visitor

Re: How to do an average of multiple columns?

Thanks. I tried this but I get an error message- The AVERAGE function only accepts a column reference as an argument

What am I missing (I'm new to Dex)?

 

Measure = AVERAGE(SUM(Table2[SAP SRM Functionality])+SUM(Table2[SAP SRM Productivity])+SUM(Table2[SAP SRM Quality])+SUM(Table2[SAP SRM Support]))

Super User
Super User

Re: How to do an average of multiple columns?

@MichalHoltz you right!

 

what about 

 

(AVERAGE(Table2[SAP SRM Functionality])+average(Table2[SAP SRM Productivity])+average(Table2[SAP SRM Quality])+average(Table2[SAP SRM Support]))/4?

 

 


Did I answer your question? Mark my post as a solution.
Proud a to be a Datanaut!
MichalHoltz Frequent Visitor
Frequent Visitor

Re: How to do an average of multiple columns?

@vanessafvg it works! Thanks a lot!!

au051663 Frequent Visitor
Frequent Visitor

Re: How to do an average of multiple columns?

Thanks it worked

 

Highlighted
Barslund Member
Member

Re: How to do an average of multiple columns?

I don't know the full model, but wouldn't it make more sense to change the datamodel into a thin fact table with App1-3 as a category, instead of building measures like this?

 

Would seem to be more alligned with best practice.