Hi y’all,
I have a “Tasks” object. Each record has a “due date” field and a “frequency” field. I also have created equation fields which add 1, 7 or 30 days to the due date. These fields are set to be formatted as “Date” fields.
I have attempted to set up a task which, when the user sets the task to “Done,” the “due date” is updated according to the “frequency” field (i.e. either 1, 7 or 30 days in the future) and the “Done” value is reset to “no”.
However, the task function does not recognise the equation fields as “date” fields, even though they are set as date fields.
Any help much appreciated.
@houwtama, here’s how I’d do it:
- Due date: A regular date field
- Frequency: A number field
- Next due date: A date formatted equation with formula:
{Due date} + {Frequency}
Your task would look something like this:
When the Due date field updates via the task, the Next due date will automatically calculate ready for the next time the task runs.
@StephenChapman many thanks for your prompt support!
So, here’s part of my record. When the user updates the “Done” field to “yes”, the “Due Date” should be updated with the date that corresponds to the “Frequency” field.
However, as you can see in image of the task below, the drop-down menu to select the applicable date field does not include any of the calculated dates.
I’ve set the calculated date field’s result as “Date” - see below.
It seems the task does not recognise the calculated dates…
@houwtama, ahh I didn’t realise you were using Next-Gen.
What I showed you was in Classic, and if I switch that to Next-Gen, it doesn’t allow you to specify any type of field as the value, which isn’t very nice!
In Next-Gen, you’ll just need to go one step further and convert your equation field back to a date field using a field conditional rule:
In your case, you’d use your Frequency logic to assign the right equation to the date field.
Then you should able able to assign that as the value in the task!
Many thanks @StephenChapman !!! 
