Hello,
I am trying to get a solve for adding a date in this list using the previous date plus the days listed in the day column. I tried the earlier function but it didn't work. Can someone explain how I can do this as a measure?
Hi,@willb006 ,thank you for your reply.
According to your latest information, you need to realize the effect of grouping calculation based on TicketID on the original basis, then you just need to change all the places in the code where ALL('Table') is used to ALLEXCEPT('Table'['ticket_number']), and let the original scope of the filter table which removes all the external filters be changed to just affected by the grouping of ['ticket_number'].
to achieve the effect of grouping (each ticket_number is counted internally).
like this:
result_column02 =
VAR _date = [comment_sort]
VAR _numnotbalnk =
CALCULATE (
MAX ( 'Table'[comment_sort] ),
FILTER (
ALLEXCEPT ( 'Table', 'Table'[ticket_number] ),
'Table'[comment_sort] < _date
&& NOT ( ISBLANK ( [wall_commentcreatedon] ) )
)
)
VAR diffday =
CALCULATE (
SUM ( 'Table'[Days] ),
FILTER (
ALLEXCEPT ( 'Table', 'Table'[ticket_number] ),
'Table'[comment_sort] > _numnotbalnk
&& 'Table'[comment_sort] <= _date
)
)
VAR lastdate1 =
CALCULATE (
MAX ( 'Table'[wall_commentcreatedon] ),
FILTER (
ALLEXCEPT ( 'Table', 'Table'[ticket_number] ),
'Table'[comment_sort] = _numnotbalnk
)
)
RETURN
IF (
ISBLANK ( 'Table'[wall_commentcreatedon] ),
lastdate1 + diffday,
'Table'[wall_commentcreatedon]
)Note that your data is quite specific and implements not really iterative logic (it looks like iteration, but it is not).
And fortunately, the source you gave has a comment_sort column to achieve an iteration-like effect (actually a conditional judgment based on sortnum, where each row is recalculated from the first row). If you don't provide a column for comment_sort, everything will get very tricky. （DAX itself doesn't support implementing iteration (it calculates uniformly based on a whole column, not on each cell, and there is no looping logic), and if the implementation wants true iteration logic, it's usually handled locally in the datasource or through Power Query using looping functions.
I hope my explanation can answer your questions.
I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi, Can you provide an example with an expected output?
Proud to be a Super User! |  |
Hello,Kaviraj11 ,thanks for your concern about this issue.
And I would like to share some additional solutions below.
Hi,@willb006 .I am glad to help you.
I have written the following code, and the end result is the same as your expected columns.
The Dax code(calculate column):
result_column02 =
VAR _date = [comment_sort]
VAR _numnotbalnk =
CALCULATE (
MAX ( 'Table'[comment_sort] ),
FILTER (
ALL ( 'Table' ),
'Table'[comment_sort] < _date
&& NOT ( ISBLANK ( [wall_commentcreatedon] ) )
)
)
VAR diffday =
CALCULATE (
SUM ( 'Table'[Days] ),
FILTER (
ALL ( 'Table' ),
'Table'[comment_sort] > _numnotbalnk
&& 'Table'[comment_sort] <= _date
)
)
VAR lastdate1 =
CALCULATE (
MAX ( 'Table'[wall_commentcreatedon] ),
FILTER ( ALL ( 'Table' ), 'Table'[comment_sort] = _numnotbalnk )
)
RETURN
IF (
ISBLANK ( 'Table'[wall_commentcreatedon] ),
lastdate1 + diffday,
'Table'[wall_commentcreatedon]
)here is my test data:
Note that the effect of iterative looping is not possible with DAX functions in power BI Desktop (if you want to achieve this, it is generally recommended that you solve it at the data source or use a looping function through Power Query)
This is actually one of the flaws in Power BI DAX (because Power BI DAX code performs the same operation based on a whole column. Whereas excel can do this easily because it can use each cell as a unit of calculation)
Fortunately, your requirement implementation is not really iterative, so it can be achieved with dax code similar to iteration
I hope my test will help you.
I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi,@willb006 ,thank you for your reply.
According to your latest information, you need to realize the effect of grouping calculation based on TicketID on the original basis, then you just need to change all the places in the code where ALL('Table') is used to ALLEXCEPT('Table'['ticket_number']), and let the original scope of the filter table which removes all the external filters be changed to just affected by the grouping of ['ticket_number'].
to achieve the effect of grouping (each ticket_number is counted internally).
like this:
result_column02 =
VAR _date = [comment_sort]
VAR _numnotbalnk =
CALCULATE (
MAX ( 'Table'[comment_sort] ),
FILTER (
ALLEXCEPT ( 'Table', 'Table'[ticket_number] ),
'Table'[comment_sort] < _date
&& NOT ( ISBLANK ( [wall_commentcreatedon] ) )
)
)
VAR diffday =
CALCULATE (
SUM ( 'Table'[Days] ),
FILTER (
ALLEXCEPT ( 'Table', 'Table'[ticket_number] ),
'Table'[comment_sort] > _numnotbalnk
&& 'Table'[comment_sort] <= _date
)
)
VAR lastdate1 =
CALCULATE (
MAX ( 'Table'[wall_commentcreatedon] ),
FILTER (
ALLEXCEPT ( 'Table', 'Table'[ticket_number] ),
'Table'[comment_sort] = _numnotbalnk
)
)
RETURN
IF (
ISBLANK ( 'Table'[wall_commentcreatedon] ),
lastdate1 + diffday,
'Table'[wall_commentcreatedon]
)Note that your data is quite specific and implements not really iterative logic (it looks like iteration, but it is not).
And fortunately, the source you gave has a comment_sort column to achieve an iteration-like effect (actually a conditional judgment based on sortnum, where each row is recalculated from the first row). If you don't provide a column for comment_sort, everything will get very tricky. （DAX itself doesn't support implementing iteration (it calculates uniformly based on a whole column, not on each cell, and there is no looping logic), and if the implementation wants true iteration logic, it's usually handled locally in the datasource or through Power Query using looping functions.
I hope my explanation can answer your questions.
I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi,@willb006 .Thank you for your reply.
Based on your description. I think the problem should be here:
Normally in the CALCULATE function, the expected value of the calculation should be an aggregated value (a single value, not just a column). This is because the CALCULATE function performs the calculation in the specified context, and if the returned result contains multiple values, DAX will not be able to determine what to do with them, resulting in an error.
The positions in the red area in the screenshot above should all be calculated using an aggregation function that returns a scalar value (i.e., a single value)
Location of the error code that I think might be wrong:
VAR lastdate1 = CALCULATE ( 'Table'[wall_commentcreatedon] , FILTER ( ALLEXCEPT ( 'Table', 'Table'[ticket_number] ), 'Table'[comment_sort] = _numnotbalnk ) )
change to this:
CALCULATE (
MAX ( 'Table'[wall_commentcreatedon] ),// use MAX function
FILTER (
ALLEXCEPT ( 'Table', 'Table'[ticket_number] ),
'Table'[comment_sort] = _numnotbalnk
)
)
I have uploaded the complete pbix file, you can view the file and do a complete error check against the code above, I have not used any other meausre in the entire calculation and there are no other table relationships and the final results are displayed properly so I think you may have missed something in the code writing process (in the calculate function, the first parameter in the calculate function must be an aggregate value, not a column name with multiple values), good luck figuring out what's wrong.
I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Helpful resources
Power BI Monthly Update - June 2025
Check out the June 2025 Power BI update to learn about new features.
Fabric Community Update - June 2025
Find out what's new and trending in the Fabric community.
