|
| 1 | +--- |
| 2 | +title: Order Taker Not Auto-Filled When Creating Purchase or Sales Orders |
| 3 | +description: Troubleshoot issues that prevent automatic field population when creating a purchase or sales order in Dynamics 365 Supply Chain Management. |
| 4 | +ms.date: 09/12/2025 |
| 5 | +ms.search.form: PurchTable, PurchTablePart, PurchCreateOrder, SalesTable, SalesCreateOrder |
| 6 | +audience: Application User |
| 7 | +ms.reviewer: |
| 8 | + - vermayashi |
| 9 | + - kamaybac |
| 10 | + - v-shaywood |
| 11 | +ms.search.region: Global |
| 12 | +ms.search.validFrom: 2021-05-31 |
| 13 | +ms.dyn365.ops.version: 10.0.13 |
| 14 | +ms.custom: sap:Purchase order procurement and sourcing\Issues with Purchase order or sales order auto-fill |
| 15 | + |
| 16 | +#customer intent: As a developer or system administrator, I want to fix an issue that prevents the order taker field from being autofilled when I create a purchase or sales order. This feature enables me to avoid having to complete field manually. |
| 17 | +--- |
| 18 | + |
| 19 | +# Order taker field not autofilled when creating purchase or sales orders |
| 20 | + |
| 21 | +When you [create a purchase order](/dynamics365/supply-chain/procurement/tasks/create-purchase-order) (PO) or sales order (SO) in Microsoft Dynamics 365 Supply Chain Management, the *order taker* (referred to as the **Orderer** in a PO and the **Sales orderer** in an SO) might not automatically populate when you expect it to. This article provides guidance for troubleshooting the required configurations to enable autofill. |
| 22 | + |
| 23 | +## Symptoms |
| 24 | + |
| 25 | +The **Orderer** or **Sales orderer** field is blank when you create a PO or SO. You expect the field to be autofilled in the order form. |
| 26 | + |
| 27 | +## Cause |
| 28 | + |
| 29 | +The **Orderer** or **Sales orderer** field is autofilled only if the current user account is associated with a *party record* that has the [**Worker** role](/dynamics365/fin-ops-core/dev-itpro/organization-administration/overview-global-address-book#party-roles) in the current legal entity. |
| 30 | + |
| 31 | +> [!NOTE] |
| 32 | +> If a user has multiple party records, only the record that's set to **Worker** in the current legal entity enables autofill. |
| 33 | +
|
| 34 | +## Solution |
| 35 | + |
| 36 | +To enable autofill, associate the user account with a party record that has the Worker role set in the current legal entity. |
| 37 | + |
| 38 | +### Step 1: Verify the issue |
| 39 | + |
| 40 | +In the target legal entity, create a PO or SO, and then verify that the **Orderer** or **Sales orderer** field isn't autofilled. |
| 41 | + |
| 42 | +### Step 2: Check the party record |
| 43 | + |
| 44 | +1. Navigate to **Organization administration** > **Global address book**. |
| 45 | +1. Search for and open the relevant party record. |
| 46 | +1. In the record, check the **Roles** section (or role-specific pages) to verify that this party record has the Worker role assigned for the current legal entity. |
| 47 | +1. If the Worker role isn't assigned to the party record, go to [step 3](#step-3-associate-the-party-record-with-the-worker-role). Otherwise, go to [step 4](#step-4-associate-the-user-account-with-the-party-record). |
| 48 | + |
| 49 | +### Step 3: Associate the party record with the Worker role |
| 50 | + |
| 51 | +1. Navigate to **Human resources** > **Workers** > **Workers**. |
| 52 | +1. Select **New** to create a worker record. |
| 53 | +1. Enter the hire date and any required details. |
| 54 | + |
| 55 | +This step creates or associates the party record with the Worker role in the current legal entity. |
| 56 | + |
| 57 | +### Step 4: Associate the user account with the party record |
| 58 | + |
| 59 | +1. Go to **System administration** > **Users** > **Users**. |
| 60 | +1. Open the relevant user account. |
| 61 | +1. In the **Person** field, link the user account to the party record that has the Worker role assigned for the current legal entity. If the **Person** field is locked because of a previous association, use the **Maintain versions** option to remove the existing relation. Then, assign the correct worker-linked party. |
| 62 | + |
| 63 | +### Step 5: Validate the fix |
| 64 | + |
| 65 | +1. Save the user record. |
| 66 | +1. Create a PO or SO, and verify that the **Orderer** or **Sales orderer** field is autofilled. |
| 67 | + |
| 68 | +If the issue persists after you verify the Worker role association, try the following steps: |
| 69 | + |
| 70 | +1. Check for duplicate party records that might be causing conflicts. |
| 71 | +1. Investigate potential customizations or extensions that could override the default behavior. |
| 72 | +1. [Capture a trace for further analysis](/dynamics365/fin-ops-core/dev-itpro/perf-test/trace-trace-tutorial), if it's necessary. This trace can help identify any underlying issues that might require technical support. |
| 73 | + |
| 74 | +## Related content |
| 75 | + |
| 76 | +- [Global address book overview](/dynamics365/fin-ops-core/dev-itpro/organization-administration/overview-global-address-book) |
| 77 | +- [Party and global address book](/dynamics365/fin-ops-core/dev-itpro/data-entities/dual-write/party-gab) |
| 78 | +- [Create new users](/dynamics365/fin-ops-core/fin-ops/sysadmin/create-new-users) |
0 commit comments