Discussions

Check out Oracle NetSuite upcoming events and conferences here
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!
We’re ringing the bell so you know what that means… LAST CALL! This is your last week to register for #SuiteWorld at our early bird special rate and save $300. Join us for our biggest event of the year and learn more about how your business can get the most out of our system. https://lnkd.in/enaAr8p8
Release 2022.2 is Coming! – Get Ready with your Release Preview Account
Attention: Customers with NetSuite Electronic Bank Payment (EBP) SuiteApp, version 2020.2 QA (ID 315896) must UPDATE (do NOT uninstall) their bundle to the Production version 2022.1 (ID 416781) by December 31, 2022. Note: If users fail to manually update the Electronic Bank Payments SuiteApp within the given time window, this version of the SuiteApp (ID: 315896) will be deprecated and the account will not be updated to Leading version (2022.1) of the Electronic Bank Payments SuiteApp. Please refer to the campaign email sent to impacted customers for more information.

nlapiCreateSearch

edited Mar 17, 2022 8:52PM in NetSuite Admin Corner 1 comment

nlapiCreateSearch is not giving correct joined results if the inner-join exceeds 1000 records. In my example I tested 2 custom record types. Type A is master while Type B is detail. There is 1 to Many relationship between Type A and B.

nlapiCreateSearch is searching on Type B records, with one field reference from Type A. The joining goes OK as long as Type B records are less than 1000.

On my end I created workaround, and got rid of the join to fix the issue

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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

Leaderboard

This Week's Leaders

This Month's Leaders

All Time Leaders