Discussions

Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Don't miss out on our Pop Quiz You only have until June 20, 2025, 11:00AM ET to comment your answers and earn rewards! Click here for more details.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
SuiteWorld 2025 registration is officially OPEN

SuiteWorld is the largest annual gathering of the NetSuite community! It will be held in Las Vegas on October 6-9, 2025. Our customers and partners look forward to SuiteWorld every year as a place to hear the latest from NetSuite, get hands-on learning, and connect with each other. Register now!

Custom fields not returned in search

edited Dec 2, 2019 3:08PM in SuiteCloud / Customization 4 comments

Here is a curious case:

We set up an API search on a custom field with the following code:

------------------------------

CustomerSearch asi = new CustomerSearch();  CustomerSearchBasic asb = new CustomerSearchBasic();  asb.isInactive = new SearchBooleanField();  asb.isInactive.searchValue = false;  asb.isInactive.searchValueSpecified = true;    SearchLongCustomField ssf = new SearchLongCustomField();  ssf.@operator = SearchLongFieldOperator.equalTo;  ssf.searchValue = 746;            ssf.operatorSpecified = true;  ssf.internalId = "custentityvsiteid";  ssf.searchValueSpecified = true;

------------------------------

Since we set searchValue EQUAL TO 746, we only expect 1 record.  Typically we set it to > 0 so we get an entire customer list.  However, because of the strange thing happening, we set it to 746 in our example.

Now.. here is the SOAP request and response from the above search:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 2 (Apr-Jun 2025)

This Week's Leaders

This Month's Leaders

All Time Leaders