How do I map custom fields from NetSuite to SQL? For example we have many custom fields on the NetSuite Customer. When I map the NetSuite Customer to SQL, I only see NetSuite fields.
Mapping NetSuite Custom Fields
- Last Post 20 March 2019
Please open your NetSuite connection and select the 'Use Custom Tables' and 'Use Custom Fields' check boxes. More information is available here:
Please tell me if this helps.
We checked metadata of your NetSuite connection and there are a lot of custom fields in the Customer table.
Please open your package, click Edit for Customer task and then click the Refresh button. Whether custom fields are available and checked? If not, please specify whether all custom fields are not available in the Task Editor or only some of them.
Looking forward to your reply.
Please specify the names of the fields which you are expecting to see in your package.
Please note the following limitations: Skyvia does not support NetSuite fields, storing array data, and does not support custom NetSuite fields having double quotation marks in their name.
The reason of the issue can be the account configuration. Please perform the following actions:
1. Go to NetSuite site and click Setup > Users/Roles > Manage Roles. Then find the user that you use when you connect to NetSuite in Skyvia. Remember the value in the Role column for your user.
2. You need to edit this role and grant various customization-related permissions. In NetSuite go to Setup > Users/Roles > Manage Roles. Find the role that we got in the step 1. and click edit for it.
3. Edit the following: Permissions > Setup. Grant the following permissions with the "Full" access Level:
Custom Body Fields
Custom Column Fields
Custom Entity Fields
Custom Event Fields
Custom Item Fields
Custom Item Number Fields
Custom Record Types
Custom Transaction Fields
Other Custom Fields
4. Save the role.
Now if you connect to NetSuite with the user with this role and select true for Use Custom Fields and Use Custom Tables in Skyvia NetSuite connection, you will have access to custom fields.
Please note that custom fields may appear not right after these actions, but after some more time, for example, an hour. When we tested this scenario, custom fields were available immediately after setting up the required permissions.