Forum Discussion
Group installments by date
Hi everyone, I've been having a problem lately with a report I am trying to build...
So I've prepared this sample data in order to illustrate my question:
| Category | payment1 | paydate1 | payment2 | paydate2 | payment3 | paydate3 |
| a | 10 | jan/19 | 27 | mai/19 | 10 | jan/22 |
| b | 20 | jan/19 | 545 | jun/21 | 20 | jan/19 |
| c | 27 | dez/21 | 10 | jan/19 | 41 | jan/19 |
| d | 545 | mai/21 | 20 | jun/21 | 14 | jan/22 |
| e | 45 | mai/21 | 30 | jan/22 | 10 | jan/22 |
| f | 27 | dez/21 | 78 | jun/21 | 20 | jan/22 |
| g | 545 | mai/21 | 10 | jun/21 | 27 | jan/22 |
| h | 87 | jun/21 | 2 | jun/21 | 0 | jan/19 |
I need to make sure that power bi knows that the paydate 1 is linked to payment 1, payment 2 to paydate 2 and so on...
Also, I want it to sum the category payments horizontally, not vertically, according to its date.
For example, when selecting category "a" and the year of 2019, I want to see the sum 10 +27 = 37.
Do I need to use dax for it?
Thanks in advance!
Hi, Anonymous
Thank you for your feedback.
Q1. There is no difference. I created the year column in Power Query Editor, and yours is created by Calculated Column, so that is why the symbol looks different.
Q2. In a general situation, I prefer to have a thin-fact-table. The first question's table was not that wide so I created a measure without connecting the tables. However, the second question's table was wider than the first one, so I wanted to transform it into a different structure to have a thin table. In this case, I could connect to the calendar table, and the measure is so simple to write.
Please check the link down below.
The result is the same as the first one, but the measure is so simple, if you transform the table structure. Transforming the table structure is easily done in Power Query Editor.
Payment Total V2 =SUM(DataV2[payment])Hi, My name is Jihwan Kim.
If this post helps, then please consider accept it as the solution to help other members find it faster, and give a big thumbs up.
8 Replies
Hi, Anonymous
Please check the below picture and the sample pbix file's link down below, whether it is what you are looking for.
The measure is in the sample pbix file.
Payment Total =
CALCULATE (
SUM ( Data[payment1] ),
FILTER (
Data,
Data[paydate1] >= MIN ( 'Calendar'[Date] )
&& Data[paydate1] <= MAX ( 'Calendar'[Date] )
)
)
+ CALCULATE (
SUM ( Data[payment2] ),
FILTER (
Data,
Data[paydate2] >= MIN ( 'Calendar'[Date] )
&& Data[paydate2] <= MAX ( 'Calendar'[Date] )
)
)
+ CALCULATE (
SUM ( Data[payment3] ),
FILTER (
Data,
Data[paydate3] >= MIN ( 'Calendar'[Date] )
&& Data[paydate3] <= MAX ( 'Calendar'[Date] )
)
)https://www.dropbox.com/s/b3yi7ct34iqoqww/justchill.pbix?dl=0
Hi, My name is Jihwan Kim.
If this post helps, then please consider accept it as the solution to help other members find it faster, and give a big thumbs up.
Linkedin: https://www.linkedin.com/in/jihwankim1975/Jihwan, you absolutely rock!!
It was exactly what I was looking for!
I just have two more questions...
The first one is concerning the calendar you prepared in order to make it work:
So, I am used to create the date columns that I need, and the "year" one is always of good use, sure!
But, I've noticed that on your pbix file, the year in your calendar table appear as:
with the ∑ symbol... Mine doesn't appear like that.
It shows like this (please note that I'm using "year" in pt here):
but once I've added the dax function you recommended, it works as well.
I am wondering if the outcome gets affected somehow...
And the second one...
What would be the best way to add one more filter to classify these payments...
Using the same example table I've provided you with, the status columns to classify the payments can appear as:
I've uploaded the example table to dropbox like you did, I hope it helps:
https://www.dropbox.com/s/t5o7c859qi9xjfi/justchill.xlsx?dl=0
Thanks again!
Hi, Anonymous
Thank you for your feedback.
Q1. There is no difference. I created the year column in Power Query Editor, and yours is created by Calculated Column, so that is why the symbol looks different.
Q2. In a general situation, I prefer to have a thin-fact-table. The first question's table was not that wide so I created a measure without connecting the tables. However, the second question's table was wider than the first one, so I wanted to transform it into a different structure to have a thin table. In this case, I could connect to the calendar table, and the measure is so simple to write.
Please check the link down below.
The result is the same as the first one, but the measure is so simple, if you transform the table structure. Transforming the table structure is easily done in Power Query Editor.
Payment Total V2 =SUM(DataV2[payment])Hi, My name is Jihwan Kim.
If this post helps, then please consider accept it as the solution to help other members find it faster, and give a big thumbs up.
Hi, Jihwan, sorry I couldn't come back to it sooner!
It took me a while to get the modifications you have done with the tables into the power query editor.
In a way it really worked, but I was hoping you could help me modifying it to an easily updatable way...
Once I add another line to it, for example, with the "a" category, I get the 0x80040E4E error and another one saying I can't have duplicate value.
Would the dax solution be an option for this updatable report?
Also, would you happen to know if including a "source column", for example containing "internal", "external" and "pending" filterable text values to the dax formula would make it too complicated?
Thank you so much so far 😄