While most of the records in ServiceNow that you might want to track in an update set are already tracked, due to a dictionary attribute called update_synch, you might just be surprised at how many types of records are not tracked in update sets! For example, scheduled jobs and scheduled script executions are not tracked in update sets, so you either need a tool like this, or you'll need to move these records over manually! Skip to the bottom of this record for a link to the download page.

Since manual work is for Peons from Warcraft III and not for developers, let's build a better solution while we laugh at the mere mortals that export-then-import their records as XML.

Perhaps you've got an exceptionally long query you'd like to run.
Perhaps you need to gobble up large amounts of data via scripted REST API.
Or, perhaps you're building a neat little UI to display an arbitrary number of records.
here are a dozen reasons why you might want to "page" through a list of records in a script, but unfortunately there hasn't been a good way to accomplish this. There are nigh-undocumented APIs like "saveLocation()", but they don't tend to work consistently, or quite accomplish our goal of pagination.

Instead, we've decided to write our own GlideRecord page-turning utility, and make it freely available here along with our other free tools. Read on for more info!

Pro Tip: If you haven't checked out our other tools yet, hover your mouse over the Tools option at the top of this page. You'll find highly useful and FREE tools, such as the Update Set Collision Avoidance Tool, the Better One-Click Approvals Tool, the Update Relocator Tool, and the Temporary Permissions Utility.