Custom Fields

populating custom fields with curl custom fields integrated with breadwinner for netsuite custom fields setup can be added to the parameter list when creating the custom url button note here that a salesforce id field has been added to netsuite and integrated into salesforce using breadwinner for netsuite the netsuite field api name is custbody sfdcid, and the corresponding salesforce custom field is ncf body sfdcid c button url \&cf text custbody sfdcid=id the parameter call for curl consists of category (cf ), type (text ), netsuite field (custbody sfdcid) and the salesforce field (id above) which holds the value which the netsuite field will be set to and why is ncf body sfdcid c not being used here? simply because that is the location where the value you are setting in netsuite is reflected back to when the value is set in netsuite, breadwinner reads that value back into the salesforce invoice record, on the invoice object as shown above passing the salesforce opportunity id, into the custom field in netsuite, and showing on the custom field in salesforce populating custom transaction fields we designate a custom field on a transaction by starting the line of the custom url as \&cf which is followed by the type of the custom field (in this case a picklist) followed by the api name of the netsuite field here is the theoretical construction button url (field value) \&cf type netsuite api name=formula field c button url (static value) \&cf type netsuite api name=123 netsuite field type type value example date date \&cf date netsuite api name=formula field c datetime datetime \&cf datetime netsuite api name=formula field c list record (lookup) picklist \&cf picklist netsuite api name=formula field c integer number integer \&cf integer netsuite api name=formula field c decimal number number \&cf number netsuite api name=formula field c currency number \&cf number netsuite api name=formula field c percent number \&cf number netsuite api name=formula field c check box checkbox \&cf checkbox netsuite api name=formula field c free form text text \&cf text netsuite api name=formula field c text area textarea \&cf textarea netsuite api name=formula field c long text longtextarea \&cf longtextarea netsuite api name=formula field c email address text \&cf text netsuite api name=formula field c hyperlink text \&cf text netsuite api name=formula field c note that the above custom fields at the header level are prepended with cf and below custom line item fields are prepended with co cf this denotes cf "custom field" and co cf "child object custom field" populating custom line item fields line items from child object we designate a custom field on a line item by starting the line of the custom url as \&co cf, which is followed by the type of the custom field (in this case, a picklist) followed by the api name of the netsuite field here is the theoretical construction button url (field value) \&co cf type netsuite api name=formula field c button url (static value) \&co cf type netsuite api name=123 netsuite field type type value example date date \&co cf date netsuite api name=formula field c datetime datetime \&co cf datetime netsuite api name=formula field c list record (lookup) picklist \&co cf picklist netsuite api name=formula field c integer number integer \&co cf integer netsuite api name=formula field c decimal number number \&co cf number netsuite api name=formula field c currency number \&co cf number netsuite api name=formula field c percent number \&co cf number netsuite api name=formula field c check box checkbox \&co cf checkbox netsuite api name=formula field c free form text text \&co cf text netsuite api name=formula field c text area textarea \&co cf textarea netsuite api name=formula field c long text longtextarea \&co cf longtextarea netsuite api name=formula field c email address text \&co cf text netsuite api name=formula field c hyperlink text \&co cf text netsuite api name=formula field c populating custom segment fields to populate custom segment fields, the structure is similar to how we pass other custom fields, but the netsuite api name starts with " cseg" instead of custbody or custcol and the type value should be a picklist example of passing custom segment field at transaction level \&cf picklist cseg region=formula field c example of passing custom segment field at line item level \&co cf picklist cseg region=formula field c