Skip to main content
All CollectionsHistorical ArchiveExtendSync for Outlook NetSuite EditionManage NetSuite Records in Outlook
FAQ: Adding custom fields to supported record types with ExtendSync Outlook
FAQ: Adding custom fields to supported record types with ExtendSync Outlook

ExtendSync Outlook | Learn how to show and expose your custom fields in the ExtendSync form for supported record types

Updated over 2 months ago

ExtendSync for Outlook NetSuite allows individual users to create and edit certain NetSuite records such as Contacts, Customers, Leads, Prospects, Tasks, and Opportunities (the list is growing).

❗️Be sure to check the troubleshooting tips at the bottom of this article if you need more help, especially if you are getting permission errors.

By default, only standard fields are displayed therefore validation will fail if the user tries to save a record that has required custom fields. To avoid this, users should configure the fields to be entered and include the appropriate required fields.

Note that at present this requires each ExtendSync user to make their own modifications.

Below is an example of a custom field on an opportunity record.

This article will show you how to do the following:


Adding Custom Fields in ExtendSync

Locate the record you desire to expose custom fields

Step 1: Click the + sign and select the record you want to create a record.

Step 2: Choose which record you would like to create. We will be using Opportunity for this example.

ExtendSync will pull the minimal set of fields required to create a record based on your NetSuite settings. Mandatory fields will be included in the list, including custom fields if you have permission. Know more about mandatory fields on this link.

💡 Note: See the list of supported record types here. Your NetSuite roles need to have permission in NetSuite to be able to use this functionality.

Step 3: Tap the Configure fields button and look for the fields then click Update.


Using Custom Form Validation

Custom forms are used in NetSuite to display specific sets of fields and enforce validation rules in the NetSuite UI. The NetSuite API does not allow ExtendSync users to simply select a form and then display the desired fields (users must follow the steps above to do this). Users can, however, select a custom form that will be used to enforce validation rules. If you have custom fields that are tied to specific forms you must either set that as your default form OR expose the custom form field in ExtendSync and then select it. Once the proper form is selected the field permissions will be respected and you will be able to add values.

Step 1: Add the Custom Form field from the list of standard fields to your form.

Step 2: While editing or creating the record choose your desired custom form for validation.

If you receive a permission error for the custom form field it generally means the field is not available on the default form assigned to you in NetSuite or that you have only one form, the standard form, in NetSuite. See the troubleshooting steps below.


Troubleshooting

Permission Error

Add Custom Fields Permission

You are trying to edit your ExtendSync form but the fields are not displayed, this is due to your role in NetSuite not having permissions.

Custom NetSuite roles do not allow custom fields to be displayed without explicitly telling them to. One step you can try is to switch to a different NetSuite role to see if the custom fields display. If none of your roles display the custom fields, then share this article with your NetSuite Admin and ask them to grant your role the required permissions.

For NetSuite Admin

Step 1: Ensure that View (lowest setting) permissions are set for the records and roles you are working with. Typically the following are added.

Under Setup Tab

Custom Body Fields

Custom Column Fields

Custom Entity Fields

Custom Fields
Custom Item fields

Custom Lists
Custom Record Types
Custom Sublist fields
Custom Sublists fields
Custom Transaction Fields

Customer Status (Optional, only when creating leads)

Custom Item Number (optional, only for Item number custom fields)

Custom Event Fields (optional, only for support case custom fields)


Under List Tab
Custom Record Entries

Step 2: Once the permissions have been added ask your user to Reload the app. See instructions here.

Note, that the new permissions may take 15-20 minutes to propagate to your role. If the below steps do not immediately work please try again after 15-20 minutes (being sure to sign out of the app and back in).

If you are still having trouble please reach out to us via the messenger icon at the bottom right.

Caching

If you receive permission errors it may be due to a caching issue which can happen when the app gets updated. To resolve this, reload the app.

Step 1: Right-click anywhere within the application.

Step 2: Choose Refresh.

Field Visibility

You may also receive permission issues because the fields you added are not visible on the NetSuite form allocated for your role. As an example, some users may not use the Lead Source field in NetSuite.

While this is a standard NetSuite field not every organization uses it. If your default form in NetSuite does not have this field on it then you can hide it in Extendsync by unchecking it in configure fields.

Step 1: Remove the field with Permission Error.

Step 2: Click Configure Fields.

Step 3: Uncheck the name of the fields you don't want on your form.

Step 4: Click Update to save form settings.

Unsupported field types (supported field types are below)

Only the field types below are supported. ExtendSync does not yet support dependent fields, ie if you have locations or classes that are dependent on the value of the subsidiary selected you will see a permission error when trying to view these fields when creating a new record. A future update will address this issue.

  • Checkbox

  • Currency

  • Date

  • Datetime

  • DecimalNumber

  • eMailAddress

  • FreeFormText

  • Hyperlink,

  • IntegerNumber

  • List/Record

  • LongText

  • Percent

  • PhoneNumber

  • RichText

  • TextArea

Did this answer your question?