Unable to find the<<CONSOLE SERIAL NUMBER>>field in the Transactions in Netsuite Search Snap

Hi All,
We are not able to find the <> field in the Transactions using the Netsuite search snap.

Thanks,
kullayappa

I’m not finding any documentation about such a field. Can you please be more specific?

And do you mean you’re looking for that field in the schema for the search criteria or in the search output?

yes, I am looking for that field.

Ok, but again, where are you looking for it? In the schema for the search criteria or in the search output?

I’m not aware of any field called CONSOLE SERIAL NUMBER and am not able to find anything like that in the WSDL or the Schema Browser. Where are you seeing this field? Can you point me to some NetSuite documentation about it?

We are looking Netsuite search Snap output ,

I have selected object is:

  1. Transaction in Netsuite Search snap ,
  2. First Snap passing input values
  3. copy of the response in third snap, in that we looking the “Console Serial number”

image

Thanks,
kullayappa

Again, I’m not clear on what field you’re looking for, as I can find no evidence of a field called anything like CONSOLE SERIAL NUMBER. Can you find it in the WSDL or any of other documentation so I know what you’re looking for? What specific types of transactions are being returned by the search?

Hi Ptaylor,

The Netsuite saved search on UI shows the custom field however we dont get that information inside the SNAP response. We do get other information exposed in the saved search

Thank You,
Sombit

Ok, this is the first time you’ve mentioned that it’s a custom field. That’s quite important to help me understand your issue. Thank you.

I think there are two different approaches for getting this field in your search results.

First, when you view the results of the saved search in the NetSuite UI, do you see a column for the custom field there? If not, try editing the definition of the custom field to enable “SHOW IN LIST”. That should make it appear in search results, both in the NetSuite UI (verify that first), and in the output of the NetSuite Search snap.

An alternative approach is to uncheck the “Return Search Columns” setting in the NetSuite Search snap. However, that might result in getting a lot more data than you really want. Here’s the documentation for that setting: “If selected, returns only the values for the required columns. This is applicable only when performing an Advanced search, which is used to execute a saved search. If not selected, this returns all the record details.”

First, when you view the results of the saved search in the NetSuite UI, do you see a column for the custom field there?
[Sombit] Yes

An alternative approach is to uncheck the “Return Search Columns” setting in the NetSuite Search snap.
[Sombit] We tried this but the custom field does not come up in the response

Thank You,
Sombit

Perhaps the value is there but you don’t recognize it because the custom field’s descriptive name (CONSOLE SERIAL NUMBER) doesn’t appear in the response. Instead, you’ll see the custom field’s “scriptId”, which starts with “custbody”. For example, for a custom field in our test account called “Delivery Instructions”, the scriptId is “custbodydelivery”, and the value appears in the output as shown below:

Actually we looked couple of times but cannot find it.
Can I share you the pipeline here

Sure, you can share the pipeline if you want, but I won’t be able to execute it against your account. It would probably be more useful to see the output of the NetSuite Search snap, and to know the scriptId of the custom field you’re looking for.

Also, can you please share a screenshot of the custom field definition from the NetSuite UI?

[CommunityQuestion_29July.docx (161.5 KB) ](http://)
Please find attached the same

Thanks, but there’s insufficient information in that document for me to understand how your search and the fields are configured, and this Community is probably not the best forum for gathering this information. Your best course is probably to work with one of our support or sales engineers on this issue from this point forward, in order to better understand the specifics of this use case.