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!
Stay in the Know
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Please note that on Friday, March 20, 2026, at 8:00 PM Pacific time, our Case Management System will undergo a scheduled maintenance for approximately 4 hours. During this time, case creation via SuiteAnswers will be unavailable and inbound calls will be routed to Customer Service.
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