Custom Fields

background this article applies to netsuite custom fields, which are not a part of the standard set of fields available in netsuite by default these custom fields in netsuite are generally created by an admin/dev and are located on entity, transaction body / line, and item fields these fields then become part of the sync process and are regularly retrieved just as standard fields are breadwinner for netsuite makes it simple to retrieve your custom field data from netsuite for use in salesforce you can see a list of available netsuite custom fields in the ‘custom fields’ section of the breadwinner for netsuite tab breadwinner can sync netsuite custom objects with salesforce and can keep them updated over time creating custom fields using breadwinner creating custom fields from netsuite in salesforce using breadwinner for netsuite is actually quite simple let's get started by opening breadwinner for netsuite in salesforce and click "custom fields" (step 1) below select the category of field (step 2), such as entity, transaction body, transaction line item, or item select the type of field (step 3), such as sales, purchase, item fulfillment, customer payment or vendor payment click the button "fetch sales custom fields" (step 4), whereby breadwinner will reach out and retrieve your current netsuite schema and identify the custom fields that exist in the category/type you've selected in the table of fields (step 5) indicate which breadwinner object(s) you would like to deploy the custom field(s) to in salesforce you can process more than one field at this time if you prefer now just click the "create xx custom fields" button shown in (step 6) by clicking 'create custom fields' breadwinner will create the custom salesforce fields based on the custom netsuite fields you have selected the new salesforce custom field label will be the same as the netsuite custom field label, however, the custom field api name will be a bit different the custom field api name in netsuite always starts with one of the following prefixes “ custentity ”, for entity fields “ custbody ”, for transaction body fields “ custcol ”, for transaction line item fields “ custitem ” or " custcol "for item fields this process will create the custom field(s), however, due to salesforce limitations and to respect your organization security, breadwinner will not expose the new custom field to users, and it does not have permissions applied providing field permissions breadwinner can’t populate the data in the new custom fields created unless the user who set up breadwinner and scheduled the syncs (aka running user) has the necessary permissions on the object and its fields so, in order to provide permissions, you can either use salesforce https //help salesforce com/s/articleview?id=perm sets object perms edit htm\&type=5\&language=en us or create a https //help salesforce com/s/articleview?id=sf perm sets overview\ htm\&type=5 and https //developer salesforce com/docs/atlas en us securityimplguide meta/securityimplguide/perm sets mass assign htm who need access to the field for example, we have created a permission set called “netsuite custom object permissions” and given custom object and field permissions in the following screenshot data availability data in custom fields created in breadwinner for netsuite, may not be immediately available do note that for historical data, the full records including their new custom fields will be retrieved during our weekly sync process however for new transactions, the data will be populated as the transactions occur by using the link "check to see if this record has been updated" on breadwinner object records, you can retrieve the new values immediately if you need to accelerate the process of retrieving historical data this can also be done by utilizing tools in the troubleshooting section of breadwinner for netsuite sorting custom fields on the line item table the transaction line item custom fields on a transaction record page (e g , sales order) are sorted based on the netsuite field api name to sort them, you can change the api names of these line item custom fields in both netsuite and salesforce by following the steps below in netsuite org, change the api name of the transaction line custom field that you want to sort for example, if you have two custom fields named "warranty start date" and "warranty end date", their api names in netsuite are "custcol start date" and "custcol end date" respectively to sort them, you can rename them to "custcol 1 start date" and "custcol 2 end date" this will ensure that "warranty start date" displays first and "warranty end date" comes next on the line item table in salesforce, if the two custom fields mentioned above already exist with previous api names, then navigate to the "netsuite line item" custom object and follow one of the following options update those fields with new names, such as "ncf col 1 start date" and "ncf col 2 end date" delete the existing fields and re create them from the breadwinner tab by following step 3 if the above two custom fields do not exist in salesforce, then follow the doc custom fields docid 4cxhm3l xetbhydjd3iar and custom fields docid 4cxhm3l xetbhydjd3iar to sync those custom field values, restart the respective object sync from the breadwinner > troubleshoot >general tab