review comments regard capture trace and party id/record addressed

Author: vermayashi

support/dynamics-365/supply-chain/procurement/po-so-order-taker-not-auto-filled.md

@@ -26,14 +26,14 @@ The **Orderer** or **Sales orderer** field is blank when you create a PO or SO.
 
 ## Cause
 
-The **Orderer** or **Sales orderer** field is autofilled only if the current user account is associated with a **Party ID** property that has the [**Worker** role](/dynamics365/fin-ops-core/dev-itpro/organization-administration/overview-global-address-book#party-roles) in the current legal entity.
+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.
 
 > [!NOTE]
-> If a user has multiple Party IDs, only the ID that's set to **Worker** in the current legal entity enables autofill.
+> If a user has multiple Party records, only the record that's set to **Worker** in the current legal entity enables autofill.
 
 ## Solution
 
-To enable autofill, associate the user account with a Party ID that has the Worker role set in the current legal entity.
+To enable autofill, associate the user account with a Party record that has the Worker role set in the current legal entity.
 
 ### Step 1: Verify the issue
 
@@ -42,34 +42,34 @@ In the target legal entity, create a PO or SO, and then verify that the **Ordere
 ### Step 2: Check the party record
 
 1. Navigate to **Organization administration** > **Global address book**.
-1. Search for and open the relevant person or party record.
-1. In the record, check the **Roles** section (or role-specific pages) to verify that this Party ID record has the Worker role assigned for the current legal entity.
-1. If the Worker role isn't assigned to the Party ID, go to [step 3](#step-3-associate-the-party-id-with-the-worker-role). Otherwise, go to [step 4](#step-4-associate-the-user-account-with-the-party-record).
+1. Search for and open the relevant party record.
+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.
+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).
 
-### Step 3: Associate the Party ID with the Worker role
+### Step 3: Associate the Party record with the Worker role
 
 1. Navigate to **Human resources** > **Workers** > **Workers**.
 1. Select **New** to create a worker record.
 1. Enter the hire date and any required details.
 
-This step creates or associates the Party ID with the Worker role in the current legal entity.
+This step creates or associates the Party record with the Worker role in the current legal entity.
 
 ### Step 4: Associate the user account with the party record
 
 1. Go to **System administration** > **Users** > **Users**.
 1. Open the relevant user account.
-1. In the **Person** (or **Contact**) 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.
+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.
 
 ### Step 5: Validate the fix
 
-1. Save the user record
+1. Save the user record.
 1. Create a PO or SO, and verify that the **Orderer** or **Sales orderer** field is autofilled.
 
 If the issue persists after you verify the Worker role association, try the following steps:
 
-1. Check for duplicate **Party ID** properties that might be causing conflicts.
+1. Check for duplicate **Party records** that might be causing conflicts.
 1. Investigate potential customizations or extensions that could override the default behavior.
-1. Capture a trace for further analysis, if it's necessary. This trace can help identify any underlying issues that might require technical support.
+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.
 
 ## Related content