With our due date clearly visible for each task, we can move on. Note that we use the DATETIME_FORMAT() formula to format our due date nicely. Once the test runs successfully, all that is left will be to turn your automation on.Īfter our automation is turned on we can see that every time we change a task's status from "Todo" to "Done" a new task will be added to our table!įirst, we'll move to the "Recurring Tasks w/ Dates" table of the embedded base above, and see that we added the due date to the primary field's formula, like so:ĭATETIME_FORMAT(, "MM.DD.YY") & " _ " & Task &" _ " & Status After adding the fields, you will want to test the automation to make sure no errors occur. Note that in the above step we pulled in the dynamic "Task" field value from our previous step (the trigger step) and set the "Status" field value to a static value of "Todo". For this example, we will be using the "Create record" action to create records in our "Recurring Tasks" table. T he "Create record" action can be configured with multiple fields using dynamic values from previous steps, or static values. When our automation runs successfully, a record will be created in the specified table. To create a new record we will make use of the " Create Record" action. The next step is where things get fun-we can now setup an action to create recurring records. Now, whenever a record enters this "Completed Task" view, which will only happen when a record's status is set as "Done" because of our filter, this trigger will fire. By using a locked view, or ensuring a locked field is involved, you can decrease the likeliness of accidentally changing a view's filtering (therefore avoiding accidental automation runs for unintended records that enter that view). We strongly recommend pairing the "When record enters view" trigger with a locked view.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |