The N+1 problem happens when a single query unexpectedly multiplies into dozens of database calls—like when fetching related records one at a time. It’s a common performance pitfall, and developers on the Now Platform need strategies to handle it efficiently.
In a recent episode of the Did You Know MVP Series, ServiceNow MVP Sachin Namjoshi walks through a solution using a DataLoader pattern inside script includes. Instead of executing 39 separate queries to fetch caller details for incidents, Sachin demonstrates how batching reduces it all to a single, efficient query.
We’ve highlighted other ways to tackle the N+1 problem in past episodes—like RLQUERY and addJoinQuery()—and Sachin’s approach adds yet another option for developers to consider.
For those who want to go deeper, Sachin also published a full blog post with the implementation details and code samples:
👉 [Read the blog post]([blog link])
Takeaway:
Whether you’re using RLQUERY, addJoinQuery, or a DataLoader pattern, having multiple strategies to solve N+1 queries helps ensure your applications stay fast and scalable.
Have you run into N+1 issues in your apps? What’s your go-to approach? Share in the comments!
