@@ -214,7 +214,7 @@ This action allows to update one of the record's (related) fields. Click the :gu
214
214
field and, in the list that opens, select or search for the field to be updated; click the right
215
215
arrow next to the field name to access the list of related fields if needed.
216
216
217
- If you selected a :ref: `many2many field <studio/fields/relational-fields/ many2many >`, choose whether
217
+ If you selected a :ref: `many2many field <studio/fields/relational-fields- many2many >`, choose whether
218
218
the field must be updated by :guilabel: `Adding `, :guilabel: `Removing `, or :guilabel: `Setting it to `
219
219
the selected value or by :guilabel: `Clearing it `.
220
220
@@ -230,7 +230,7 @@ the selected value or by :guilabel:`Clearing it`.
230
230
Alternatively, you can also set a record's field dynamically using Python code. To do so, select
231
231
:guilabel: `Compute ` instead of :guilabel: `Update `, then enter the code to be used for computing
232
232
the field's value. For example, if you want the automation rule to compute a custom
233
- :ref: `datetime field <studio/fields/simple-fields/ date-time >` when a task's priority is set to
233
+ :ref: `datetime field <studio/fields/simple-fields- date-time >` when a task's priority is set to
234
234
`High ` (by starring the task), you can define the trigger :guilabel: `Priority is set to ` to
235
235
`High ` and define the :guilabel: `Update Record ` action as follows:
236
236
@@ -307,8 +307,8 @@ triggered the creation of the new record.
307
307
308
308
.. note ::
309
309
The dropdown list related to the :guilabel: `Link Field ` field only contains :ref: `one2many fields
310
- <studio/fields/relational-fields/ one2many>` existing on the current model that are linked to a
311
- :ref: `many2one field <studio/fields/relational-fields/ many2one >` on the target model.
310
+ <studio/fields/relational-fields- one2many>` existing on the current model that are linked to a
311
+ :ref: `many2one field <studio/fields/relational-fields- many2one >` on the target model.
312
312
313
313
.. tip ::
314
314
You can create another automation rule with :ref: `studio/automated-actions/action/update-record `
0 commit comments