Before using an already existing netsuite connection, refresh metadata needs to be done on it. Make sure the last refresh status is complete for the connection.
This feature exposes custom fields for standard objects as named fields in the mapper and during netsuite endpoint creation for advanced search and saved search operations. This feature applies to all basic(except delete) and search operations of netsuite. And for both sync and async processing modes.
For Basic CRUD operations, the custom fields is exposed on the mapper as a named field. The custom field name is derived from the name given to custom field in netsuite. This makes it easier to map without needing to know the internalId and scriptId of a particular custom field for standard object. For eg, here is the mapping done for netsuite update operation. The image below shows a request mapping from Rest(trigger) to Netsuite Update operation on Customer Standard Object .
You can check that there are two fields that have been mapped for the netsuite update operation. ICSEmailId and AdvertisingPreferences. ICSEmailId is a simple type custom field, no further work is required on the part of the integration developer. Just use it like any other simpletype field. AdvertisingPreferences is a complex type custom field. It correlates to a multiselect custom field in netsuite. For complex type custom fields, listitemId correlates to the internalId of the listItem. For the invoke request to netsuite update operation to succeed, integration developer needs to ensure listItemId value is mapped. For mapping more than one listItem, just repeat the ListItem and do the required mapping. Read the complete article here.
For regular information on Oracle PaaS become a member in the PaaS (Integration & Process) Partner Community please register here.