From 8be6d9e43e84535fd6267c9a26cade05514856c4 Mon Sep 17 00:00:00 2001 From: Benoit Socias Date: Tue, 27 Jun 2023 08:37:16 +0000 Subject: [PATCH] [FIX] howto/rdtraining: ch.13 adapt reference to salesperson field In chapter 13 the `property_ids` field is defined as the inverse of a `user_id` field. But in chapter 8 when the salesperson field is added, no such name is given to it. This commit adapts the description to reference the general concept of the field used to link to the salesperson instead of an actual field identifier. task-3381757 closes odoo/documentation#4909 X-original-commit: 3a131c829a6440e017fe692eb10abc1a02a0c245 Signed-off-by: Antoine Vandevenne (anv) --- .../tutorials/getting_started/13_inheritance.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/content/developer/tutorials/getting_started/13_inheritance.rst b/content/developer/tutorials/getting_started/13_inheritance.rst index dbf707785..bf1fe5ac0 100644 --- a/content/developer/tutorials/getting_started/13_inheritance.rst +++ b/content/developer/tutorials/getting_started/13_inheritance.rst @@ -151,11 +151,12 @@ By convention, each inherited model is defined in its own Python file. In our ex - Add the following field to ``res.users``: - ===================== ====================================================== + ===================== ================================================================ Field Type - ===================== ====================================================== - property_ids One2many inverse of ``user_id`` to ``estate.property`` - ===================== ====================================================== + ===================== ================================================================ + property_ids One2many inverse of the field that references the salesperson in + ``estate.property`` + ===================== ================================================================ - Add a domain to the field so it only lists the available properties.