Forum Discussion
Sum with Grouping
Are the groups static, or do they need to be dynamic based on a user selection?
If they're static, it's easy. Make a new field (preferably at your data source if you can, else in a query (e.g. in Power Query) before the data is added to the Power Pivot model) with those groups. Then you can just create visualizations against the new field that contains the group.
If they must be dynamic based on user selection, you'll have to give us some more detail on what your expected use case is, and the solution will be a bit more complex.
Hi everyone again,
I am being tasked with producing some financial reports using Power BI. One of the reports is Receivable Aging. The two columns to be used in the Receivable Aging report are Amount Due and Due Date. The Aging periods are 0-30 Days, 31-60 Day, 61-90 Days, Over 90 Days.
I was able to extract the aging days, DurationDays, for each row, but I don't know how to create new tables for each of the aging periods.
My previous example has been simplified. The example below is much more realistic:
Amount Due Due Date
$100 1/16/2016
$200 2/16/2016
$300 5/14/2015
$400 7/25/2014
$500 1/9/2016
$600 5/12/2015
$700 6/4/2016
Expected Report:
Aging Amount
0-30 $500
31-60 $0
61-90 $0
Over 90 $1,300
Also, would you recommend a book on DAX, Power Query, with an emphasis on programming?
Many thanks for your help again.
The DAX version of this is:
Aging = IF(TODAY()-[Due Date]<=30,"0-30",IF(TODAY()-[Due Date]<=60,"31-60",IF(TODAY()-[Due Date]<=90,"61-90","Over 90")))
One note, this DAX version, nor I believe the "M" version from greggyb will give you the $0 values. So if you only have buckets of "0-30" and "Over 90", you will not see the "31-60" and "61-90" categories with $0. There are a number of techniques around that, you could create a separate "Enter data" query to add in a $0 value that falls into each category and merge it with your data feed for example, then you would ensure that you have all of the categories listed but it wouldn't affect your final sums.
See the comments area from my recent blog post, there is discussion around good DAX resources, etc.
Greg_Deckler Just FYI, the Tabular storage engine can perform better compression on "native" columns than it can on calculated columns. Generally it is best practice to perform all ET before the L into the data model.
greggyb No argument there, however, as an end-user focused tool, I think it is useful to present DAX solutions as well. DAX is a language that someone with passable Excel formula skills can master relatively easily. "M" on the other hand requires more of a coding background in my opinion and has a significantly higher learning curve.
I don't tend to be a fan of absolutes. If I am building a model for a customer, I have to take into consideration their ability to maintain it and extend it over time. In addition, there is the case where if I am going to have to use DAX, as is sometimes the case, I'll often end up doing it all in DAX from a simple maintainability perspective. Nobody likes to work on a product that is half written in C#, half in Java and half in Perl, that's just not enterprise grade.
I think it is a good idea to remember the target audience for this community, not everybody is a pure BI professional and there are multiple things to take into consideration rather than a few select people deciding on a "best practice". "Best practice" for IT professionals, sure, "best practice" for your standard business end user, not necessarily.
It's always good to have multiple options and perspectives.
Greg_Deckler, I apologize if I came off as if I were criticizing you. That was not my intention. You are consistently one of the most helpful posters on this forum, and I was just taking the opportunity presented by your comment to bring up a point that I find to be important.
To be honest, I expected that you would be aware of the tradeoffs between DAX calculated columns and "native" columns, but your comment prompted the thought, so I addressed it toward you so other readers would understand what I was replying to.
I agree that multiple options are important, as some things which are cumbersome in M are trivial in DAX and vice versa, so for any data professional (and I do not intent this term to be exclusively referencing IT resources or BI folk), it's worth learning both, even if only at the level of primitive operations on basic types.
Smoupre: Appreciate all your help on this forum!
I am trying to follow your instruction here. My DAX command looks like this:
Aging = IF(TODAY()-jvw_Bill_AR_List[DaysOverdue]<=30,"0-30",IF(TODAY()-jvw_Bill_AR_List[DaysOverdue]<=60,"31-60",IF(TODAY()-jvw_Bill_AR_List[DaysOverdue]<=90,"61-90","Over 90")))
(The table is "jvw_Bill_AR_List" and the column is "DaysOverdue".)
When I do this, I encounter the error message:
"A single value for column "DaysOverdue" in table "jvw_Bill_AR_List" cannot be determined. ...(etc.)"
Any advice? Thanks.
MojoGene Are you trying to create a Column or Measure?
This should work if you are trying to create a Column!
Look at my answer here...
http://community.powerbi.com/t5/Desktop/Combining-2-different-if-statements-in-one/m-p/31388#M10802
Sean:
Bingo! That was it. As a novice in this, I am still perplexed by the difference between measures and columns.
Thanks for your help.
