Forum Discussion
Yes Supratim I am still seeing the same behaviour even with the NS Upsert Snap.
Hi Vikas2022 In such case you can validate your request from NS (Setup -> Integration _> SOAP Webservices log ). If your request doesn't contain that change then there would be chance of some NS internal script rans behind the scene while you update that particular NS object. Ask NS team to validate. I have faced same kind of issue before.
- Vikas20222 years agoNew Contributor II
Hello Supratim Thanks for the information. So in Salesforce, I had just updated the phone field yet in the NetSuite's request.xml along with phone I could see the Address section code included, so Snaplogic is resending non-changed fields data as well in NetSuite via Update/Upsert SNAP which is resulting in duplicates.
<ns1:addressbookList replaceAll="false"> <ns1:addressbook> <ns1:defaultShipping>false</ns1:defaultShipping> <ns1:defaultBilling>true</ns1:defaultBilling> <ns1:addressbookAddress> <ns4:country>_austria</ns4:country> <ns4:addr1>Carinthian Street</ns4:addr1> <ns4:city>Vienna</ns4:city> <ns4:state/> <ns4:zip>1010</ns4:zip> </ns1:addressbookAddress> </ns1:addressbook> <ns1:addressbook>
How can I avoid this?