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
Thanks! I didn’t know this. It’s odd that it works the way I did it for some types like String. We’ll have to adjust our custom fields code to handle null values this way.
That would actually be really fantastic, because I’d love to completely scrap my custom SOAP setup.
While I have your ear, is there any chance you can also file a bug related to the names of custom columns? When you enter raw text for custom columns, it changes the definition after saving & reopening the snap to being [object Object] instead of what’s expected. The only way to save it properly is to click through the auto completed column name when the Snap processes the SOAP API, which is extremely, extremely painful to do since it takes a long time to load every time.
Our custom fields support has been overhauled in our new release. The full names of the custom fields (not their script IDs) are now integrated into the input schema of the snap so that you can map them in the Mapper attached to its input, just like standard fields. They appear under “customFields” where applicable, at the root level and inside any applicable sublists. Basically, wherever you would have previously seen the standard but unusable “customFieldList” array, which we now hide. When you map values to “customFields”, the snap will transparently map them to the right places in the “customFieldList” in the SOAP request, along with their internalIds, etc. I think you’ll find this is a great improvement over the Custom Fields table in the snap settings, which still works but is now deprecated – you won’t even see that table for a new instance of a snap, or for an instance which didn’t already have values in the table.
Awesome, glad to hear it! I’ll come running back here if I ever have any issues 😉
James, I’m happy to say we’ve released a patch for the NetSuite snap pack, netsuite7779, which addresses this issue. The NetSuite update/create snaps now handle null field values correctly, for both standard and custom fields, by sending a request with these fields listed in the nullFieldList. Your workaround to set the nullFieldList explicitly should no longer be necessary. This build is available as the Latest netsuite version in the production and uat environments.
