Soap Execute snap - Account creds in header
I’m building a custom SOAP Execute snap to replace Netsuite snaps to work around a limitation with custom fields in Netsuite snaps that require fields entered to not be null.
I’ve modeled my SOAP e...
Forum Discussion
Can you please say more about this? I’m not sure what you mean. If you set a custom field to null, the previous value is removed.
Have you tried doing this with the 4.16 version of the custom field functionality, where the values are mapped like standard fields in a Mapper in front of the NetSuite snap?
Date types are not parsed properly in custom body fields and thus if you want to use the standard snaps you cannot use null values.
Interesting. Is there a support ticket about that issue?
IIRC I tried to report this as a part of asking for help with a workaround.
I think there was another issue relating to null fields still not being updated properly which is why I also did this. I mean, I asked this over a year ago, lol.
It’s probably worth checking it out as it is definitely still a problem or is at least ticketed - I almost did this workaround again very for a much more complicated series of Netsuite SOAP calls but gave up when I realized I didn’t actually have to change the number of date columns we’re already splitting calls across, and it doesn’t need proper updates as we expect only to create new Netsuite objects using the process.
