i'm doing my first suitelet and rendering a sublist of orders from a saved search. according to suitelet best practices in help I should be implementing pagination. That makes sense, but i need to submit the entire set of search results when a user clicks submit, not just the page they are viewing. is it possible to have the data loaded but only render a subset of the search results so that when you do a POST, it sends all the data. I feel like that won't work because the POST sends only what's in the sublist and if i haven't added it to the sublist, it won't be sent. does needing to send the whole dataset render pagination moot? I suppose I could render only a subset on GET but on POST reload the entire search. the issue with this is that I want to know I'm only submitting current information and if I'm continually reloading the search in POST, new information may drop in (or out) the user wasn't expecting. I hope I described this clearly, if not, let me know. Any insight is appreciated, thanks!

The dataset you use to populate the sublist can be used as the body of the POST. Also consider just sending the IDs and not the whole dataset if that's possible. The less data you have to send via POST the more efficient it will be.

thanks, that's what happening, the POST request ends up creating a PDF of orders to be printed via Advanced PDF and the data sent gets added to that template as a custom data source, so unfortunately I have to send more than just ids. your message confirms that in order for data to be sent in the POST body it has to be in the sublist, so I can't use pagination in my use case if i don't want to risk the data changing between GET and POST.