the subsidiary ship to address has been updated bu...
# ask-stanley-ai
m
the subsidiary ship to address has been updated but when creating a new PO it defaults the old ship to address. why is this ?
c
AI generated answer (using internal Slack threads):
The issue you're experiencing where the subsidiary's ship-to address has been updated but when creating a new Purchase Order (PO) it defaults to the old ship-to address, could be due to several reasons: 1. Location Record: In a OneWorld account, the Shipping Address on a Purchase Order record is usually sourced from the Location record. If the PO is created from a Sales Order (dropship), it will be the shipping address on the Sales Order Transaction. If you have old addresses in your Locations, it might be causing the issue. 2. Order of Setting Fields: In dynamic mode, the order in which you set fields matters. If you're setting something else after the address that's causing it to get wiped, it could result in the old address being used. Common fields that should be set first include subsidiary, customer, department, class, location, and account. 3. Workflow or User Event Scripts: Check if you have any workflow or user event scripts on beforeSubmit in a create context only that might be making the edits and causing the old address to be used. 4. Custom Address Setting: If you're setting a custom ship-to address in a Sales Order, it can be done beforeSubmit. However, the address text related fields on the transaction tend not to update from their original values. You can update the transaction's address text yourself or use Record.removeSubrecord before setting the subrecord fields to force NetSuite to automatically source the address text. Remember to check these points and update the necessary fields or scripts to ensure the new ship-to address is used when creating a new PO. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******
Slack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.834555149
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.831379235
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.830198765
Please provide your feedback on this answer.