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.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Make Your Voice Heard: What Tech & ERP Topics Should We Explore in our Next Webinar?? We’re all ears! Vote now, and the poll runs until January. Poll for ERP | Poll for Tech.
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!
To help you get the most out of your 2025.1 Release Preview account, review the topics outlined in the Release Preview Guide.
NetSuite Release 2025.1 Release Notes are available for download here!
Using Dataset.runPaged or query.runSuiteQLPaged returns empty pages in between populated pages
If I run the following query in the SuiteQL suitelet,
SELECT COUNT(*)
from inventoryitemlocations
WHERE
averagecostmli IS NOT NULL;
Then It returns 16869, so that means there are 16,869 rows.
I want to provide a CSV export that gets emailed to users on a scheduled basis, of all the data that would be there if it was SELECT * instead of SELECT COUNT(*)
However, when I create a suitescript to do this, I get much smaller numbers of rows.
If I use Dataset.runPaged, some of the pages (pageSize = 1000) are completely empty. These empty pages appear after several populated pages, and before other populated pages.
Tagged:
0