Up front, something that would be great to know is:
Is this flow *purely* existing to notify the user?
Also, thanks for this information. It might require another user's help, because I'm unfamiliar with the fields available, but what you'd be wanting to look at leveraging here are what the Case Status *was* and what it currently is.
Based purely on what I know, then I have a really basic solution ...
Basic Solution - Add A 'previousStatus' Column / Field
So if I wanted to be particularly basic about it then I would:
- Add a 'previousStatus' column/field in the Dataverse to compare to
- Then either:
- If the flow is purely for notifying - Don't trigger if 'Status' and 'previousStatus' both equal "Closed"
- If it does more - Add a first step to check if it has changed, and if it has changed from "Closed" to any open status.
That way you can either save a flow run if this is purely a notifier flow, or continue on to do whatever else that needs doing including any possible notifications.
Optional - Boolean Variable
If this flow is for other stuff, and you maybe need to know whether the status is re-opened for other parts of the flow, you could also create a 'reopenedVAR' Boolean Variable action, with a default "false" value. Then if it's been re-opened, you can switch that to "true" and take other paths later in the flow for other stuff.
--------
Potentially Complex Solution - Leverage Any Dataverse Versioning
Alternatively, if (and I've not looked into this functionality) Dataverse offers versioning akin to what you can use on SharePoint lists (or with files in SharePoint libraries) then you can run logic to check the previous version's status, and if both this version and the previous are 'closed' then you've no need to either perform the action, or (if you're being super clever) trigger the flow.
