Picklist and Lookup Fields

for both picklist fields and lookup fields, netsuite requires the id value during record modification or creation please be aware that in netsuite, a user may be familiar with selecting from a dropdown/picklist menu and looking for a text value however, the data passed to netsuite by breadwinner must be a numeric id (please note this is the opposite of salesforce, which requires the text value when populating a picklist) finding the id of standard picklists the ids of netsuite standard picklists can be found in different locations some of the possible places these standard picklist values can be found include setup > accounting > accounting list setup > sales > crm list setup > company > department setup > company > classes for instance, the department and class picklist can be found in their respective locations under the company setup however, other picklists will be in other locations finding the id of custom picklists the ids of custom picklists can be found under customization > lists, records & fields > lists note if you can’t see the picklist id, please go to the section exposing picklist ids in the docid\ mskh pfwthgpcpa64rotf here is an example picklist please note the internal id column populating netsuite picklist and lookup fields you will need to pass the internal id to breadwinner, rather than the value you can pass this as either a field that contains the internal id (formula fields work well for this, as they can be based on a salesforce picklist) or you can pass this to breadwinner as raw data within the custom url itself without creating any fields (only an appropriate choice if you always use the same value) populating standard lookup fields once you have the id of a standard field, you can pass it to breadwinner either as a field or as a value as an example, here is a standard picklist, department button url (field value) \&department=department api field c button url (static value) \&department=123 and here is the class field being populated button url (field value) \&class=sales order class api field c button url (static value) \&class=123 here is the subsidiary field mapping button url (field value) \&subsidiary=subsidiary api field c button url (static value) currently, static value not supporting for subsidiary param populating custom lookup fields netsuite custom picklist and lookup fields present an additional layer of complexity for netsuite standard picklist and lookup fields, simply passing the id is enough however, for custom fields, netsuite requires that the field type be specified and, thus, breadwinner requires the field type to be specified to specify the field type, we require additional information in the custom url picklists have the type picklist and we require this to be in the custom url only active internal ids shall be passed to netsuite the ones with inactive checkbox checked are not accepted by netsuite for transaction custom fields (for clarity, in netsuite a ‘transaction’ is a sales order, estimate, or invoice) 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 \&cf type netsuite api name=formula field c for the sake of readability, we have added italics and bold to different parts of the query string the italic text refers to the netsuite field type which may be one of picklist, string, integer, date, and so forth the bold text refers to the netsuite api field name itself obviously, you will not need italics or bold in the actual formula when you create it an example query string in real world usage, where a picklist is specified, might be button url (field value) \&cf picklist custbody revenue=formula field c button url (static value) \&cf picklist custbody revenue=123 where picklist refers to the netsuite field type and custbody revenue refers to a custom field on the sales order (or any transaction object) called “revenue” for line item custom fields netsuite transactions (invoices, sales orders, estimates, and credit memos) all have line items while there are several ways to pull data from salesforce to populate that line item, the usual way to populate that line item in netsuite is to use a child object (i e a related list) on the originating record in salesforce we designate a custom field that is pulled from a child object and should go onto 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=234 for the sake of readability, we have added italics and bold to different parts of the query string the italic text refers to the netsuite field type which may be one of picklist, string, integer, date, and so forth the bold text refers to the netsuite api field name itself obviously, you will not need italics or bold in the actual formula when you create it an example query string in real world usage, where a picklist is specified, might be button url (field value) \&co cf picklist custcol revenue=formula field c button url (static value) \&co cf picklist custcol revenue=123 where picklist refers to the netsuite field type and custcol revenue refers to a custom field (column) on the line item called “revenue”