​DATA / SEARCHES / REPORTS

---

getValue vs getTexgt

I recently ran across a quirky situation where a script was parsing through the data in a Saved Search. The script was referencing the search (search.load({id}) and was loading 1,000 records per page (mySearch.runPaged({pageSize: 1000}).

The problem we encountered was that the data around the page range change was wonky: some fields were replicated some were not. So the data was incorrect and the totals were not lining up. We had two solutions:

#1 - Add uniqueness to the Saved Search - one way to solve this was to add an additional level of uniqueness to the Saved Search. Once every line was unique, the problem went away.

#2 - getValue vs getText - NetSuite suggested we were retrieving the values using the wrong retrieval. They said if we changed from:

result.getValue(columns[j]) to

result.getText(columns[i]) it would resolve. Makes sense as the ids were duplicated but the values were unique.

---

DATA SCHEMA(s)

Which data schema tool to use? Sometimes I find myself lost looking up data in the wrong tool. Here is a quick cheat list for what to use when:

Schema Browser: Ideal for integrating Netsuite with external systems via SOAP (SuiteTalk)

Records Browser: Essential for scripting and automation within NetSuite (SuiteScript)

Connect Browser: Perfect for SQL-based analytics and reporting outside NetSuite (SuiteAnalytics Connect)

Records Catalog: General data schema including customizations

Bonus! - Use the Connect Browser for legacy NetSuite.com connectivity, use the Records Catalog for the newer NetSuite2.com data source.

---

OTHER REFERENCE NUMBER

I always have the hardest time finding the field 'Other Reference Number.' Often used to reference back to a customer or vendor document number.

In searches, this field is labeled: PO/Check Number and is listed at the top of the 'Ps' in the collating sequence.

---