I know there was an issue a few years ago about time-dependent workflow rules still firing when no longer meeting criteria. However, it was apparently fixed, but we are still having the issue. Here is a screenshot of my rule:
I am wondering if the trouble is because the field we are having issues with is "Date of Discharge" which is a formula field on a parent record.
It's important that we're not getting a bunch of email alerts about youth who are no longer in our care. So, we want to make sure they are still active. This is documented elsewhere in the database. So, I added a formula field that pulls that information on the youth's case management record. Is that field the issue or does anyone else see another problem? We are still getting email alerts for youth who are discharged and whose date of discharge field is NOT null.
Thank you!
2 件の回答
Yes, the Date of Discharge field is the problem. A workflow rule cannot run based on a formula field because the value is not actually stored in the field, so it doesn't change. To get around this, you could change the formula field to a regular date field, and have a Workflow Rule do a Field Update on it to get the value from the other object (make sure to have it re-evaluate Workflow Rules after that Field Update). Then, the Workflow Rule above should work.
Or, possibly, instead of referencing the formula field in your Workflow Rule, could you instead reference the actual field that the Date of Discharge formula field is mirroring?
