what types of changes on an addressbook could make...
# ask-stanley-ai
l
what types of changes on an addressbook could make a system note of field "Address" in the customer where old and new value (the address string) is the same, (default shipping, default billing, label, residential address, a custom field on the address book form?).
c
AI generated answer (using internal Slack threads):
Based on the conversations, it appears that changes to an addressbook that could result in a system note of field "Address" in the customer where old and new value (the address string) is the same could include: 1. Default Billing Address: If the default billing address is changed, it may not be captured in the system notes if the change is not made directly to the address. However, if a new address is created and assigned as the default billing address, it replaces the address at the header level and can be captured in a saved search comparison, but not in the system notes. 2. Default Shipping Address: Similar to the default billing address, changes to the default shipping address may not be captured in the system notes unless the change is made directly to the address. If a new address is created and assigned as the default shipping address, it replaces the address at the header level. 3. Label: Changes to the label of an address may not be captured in the system notes. 4. Residential Address: Changes to whether an address is marked as a residential address may not be captured in the system notes. 5. Custom Field on the Address Book Form: Changes to a custom field on the address book form may not be captured in the system notes. In all these cases, the system notes seem to only capture changes to the current billing address. If a new address is created and assigned as the default billing or shipping address, it replaces the address at the header level and can be captured in a saved search comparison, but not in the system notes. ****** 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.869437516
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.862631679
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.860359967
Please provide your feedback on this answer.