Forum Discussion
AustinK
3 years agoQrew Commander
Just keep in mind that automations is going away in the really not that distant future. In June 2022 they will restrict you from making new automations. In January 2023 all automations will cease to function. You may create some tech debt for yourself here that will be annoying later on so at least write it down I guess. Then again maybe you can migrate the automation to a pipeline easily with their system, who knows.
It sounds like all you need to do is to trigger on the Estimates table when a record changes. Assuming I understood you correctly I think this would work:
Trigger: When a user modifies a record in Estimates.
Action: Modify records in Patients where Record ID# is equal to Trigger: Related Patient(old or new value should not matter).
Set Reminder Date as <insert date here>, You can either pick a date or have a formula that gets you the right date ready to go.
It sounds like all you need to do is to trigger on the Estimates table when a record changes. Assuming I understood you correctly I think this would work:
Trigger: When a user modifies a record in Estimates.
Action: Modify records in Patients where Record ID# is equal to Trigger: Related Patient(old or new value should not matter).
Set Reminder Date as <insert date here>, You can either pick a date or have a formula that gets you the right date ready to go.
- KellyLyons13 years agoQrew CadetHi Austin!
So I have set this up, and the automations run details are showing that the status is complete however I do not see that the specified field is updated.
Here are the screen shots of the set up. The only difference from what you said above is that My reminder date is already an existing date field, so I do not need to insert it. I have set it change based on the pictured parameters. Any ideas what is the issue??
------------------------------
Kelly Lyons
------------------------------