Help Please with Calculated Table Logic

[Anonymous]

Hi all,

Looking for some help to think through this dax calculation I'm trying to come up with:

I have robot log data based on queues for a couple of months. Each line item is a transaction of some sort. It could have a status of Successful, failed, abandonded, retried. For all of the cases that have retried, they try again and again until it goes to successful, failed, or abandonded.

This is what I want to do: I'd like to summarize a new table with ALL 'keys' that have "retried" at least once, then retrieve the MAX date of that KEY to see what the outcome at the end was. It'll never end on retried. It'll end up being Successful, Failed, or Abandoned. I hope this is somewhat clear:

Here are the useful/relevant fields I have: Key, status, started, ended, transaction execution time, etc.

Would appreciate anyones input.

Thank you!

[PaulDBrown]

Sorry, I should have been more specific...Please provide sample data in table format (as in data). We cannot work on an image. Thanks!

[Anonymous]

Will a CSV file work?

[V-lianl-msft · Accepted solution]

Maybe I see what you mean. Please try the DAX below.

Table = 
FILTER('Table (2)',
'Table (2)'[Date]=CALCULATE(MAX('Table (2)'[Date]),ALLEXCEPT('Table (2)','Table (2)'[Key]))
&&CALCULATE(COUNT('Table (2)'[Key]),ALLEXCEPT('Table (2)','Table (2)'[Key]))>1)

For more details, please refer to the sample .pbix.

[PaulDBrown]

please provide some sample data and the expected output. Thanks!

[Anonymous]

Here are all of the relevant fields here. Key, Status, Ended, Exception Reason. For any cases where there are 'Retries' in 'Status' column, that means that there are duplicates in the Key column. I want some sort of outcome like this:

So it'll show me any keys that once were retired, it retries the MAX date of all retried cases which tells me what ended up happening int he end. PLease let me know if this is enough information.