Calculating Date/Timer Differences Dynamically

This seems to be working as intended. Thank you for your help. Currently, the dataset is small, but it is expected to grow signifactly in time. We do not currently have a finalized retention policy. Would you be able to provide the measure as an alternative?

I wanted to thank you for your help on the referenced inquiry. It worked flawlessly.

I'm faced with another issue related to this inquiry. We have responses labeled 'Recalled'. This response can occur AFTER approval responses have taken place and can occur multiple times during the quote approval process. In the screenshot I provided below, you can see the RECALLED response occurs after two approvals.
Is there a way to filter the ‘CALCULATETABLE’ argument to only include ‘APPROVED’ responses after the Max RESPONSE DATE of ‘RECALLED’ response if a quote number/quote version contains a ‘RECALLED’ response?
Essentially, we’d be checking to see if a quote number/version contains a RECALLED response. If it does not, our existing DAX works as intended. If it does, we’d need our virtual table (CALCULATETABLE argument) to only include the ‘APPROVED’ responses after the max RESPONSE DATE of RECALLED response. Again, from there, our existing DAX logic would work because as you can see in the screenshot provided below, the submission date for the quote number/quote version reflects the timestamp of the latest submission (occurring after the last RECALLED response).