Creating a waterfall: was in, now in

I have data which shows all caseID’s and the different statuses they have been in (including the date of the status). What i want to create is something which shows:
On 23rd Jan 2024, we had x amount of cases apply (for a loans). At the end of the day, these were the statuses they were on. A week later (1st Feb 2024) those x cases are now in the following statuses.

So the end result would be 2 waterfalls. One showing all the cases and what statuses they were in (an older date). A second showing the same cases, but what statuses they are now in (a new date).

How would i tackle this analysis?

HI @HarveyB-B

do you have some sample data or atleast a field list to work with?


waterfall was:is

So using this data, i want a waterfall of all the cases who applied on the 23rd, and the statuses they are in.

And then i want a separate waterfall which now shows those same cases a week later, and what statuses they are now in.

I’d prefer it as a waterfall, but if not the best, other ideas like a bar chart or something will be fine.


  1. your requirement would be that:

Right? Or do you want to see the caseids as well?

  1. the same 1 week later

But right now, you cant be sure the 49 cases are the same as one week earlier or can you?

I’ve realised that i messed up the dataset. All dates are recorded in datecreated, but there is a caseid, datecreated, and status every day. I think this is something we need to fix on our end so we can distinguish between a date a case was created, and a date a case was updated.

Yes, i guess you need an “dateupdated” or something.

the only thing i can think of is a calculated field of min date, which will show date when the case was created.

So get the dates where the MinDate was 23rd feb, and show casestatuses then.
Now get those same cases and show their current status.

I think this second part is harder. As other than stating the case ID’s i want to capture, i think there is no other way to get those exact cases to only show

Hello @HarveyB-B and @ErikG !

@HarveyB-B were you able to find a solution or workaround for this issue or are you still working on it?

From the activity in the thread it sounds like you may need to create a new field in your dataset.

We have parked the reporting on this data due to lack of data, so this post can be archived

1 Like