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 Question of the Week! You only have until tomorrow, November 6, 2025, 2PM ET to comment your answers and earn rewards! Click here for more details.
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.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more

Error fetching second page of transaction summary data using Token-based authentication

edited Dec 2, 2019 2:59PM in SuiteCloud / Customization 2 comments

I recently ran into issues when using an integration record with TBA to request for multiple pages of transaction summary records when using the getPostingTransactionSummary web services action.
I found the first request was consistently successful, but following requests for successive pages would fail giving the following error:  [INDENT]For pages > 1, search parameters must match the original search exactly[/INDENT] I followed the suggestions in SuiteAnswer 33416 labeled "getPostingTransactionSummary returns an error: For pages > 1, search parameters must match the original search exactly". I then ensured we were requesting the first page first, ensured no field or filter parameters had changed, and was requesting the second page immediately.

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 4 (Oct-Dec 2025)

This Week's Leaders

This Month's Leaders

All Time Leaders