megaphone
Update your Profile with your Support type to get your Support Type badge.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Stay in the know of how NetSuite can help grow your business with our guides, webinars, and events. Subscribe Here
What Topic Should We Cover Next? Your idea could be our next feature—drop your suggestion now!
No Limits. Just possibilities. Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Discover what's next at SuiteConnect Tour 2026.
Try Intelligent Payment Automation – Fee Free For Your First Month For more information, visit this thread.

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

Scheduled Script concurrency control?

edited Dec 2, 2019 6:15PM in SuiteCloud / Customization

Hello!

Can optimistic locking be achieved when reading and later updating transactions lines?

Business Requirement:
Based on sales order lines creation/updates many custom record lines needs to be updated.

Planed solutions design:

A Scheduled Script will:
1, search (nlapiSearchRecord) all new or updated sales order lines
2, loop and load (nlapiLoadRecord) sales order records
3, based on every sales order line, 1-200 custom records needs to be updated.
4, nlapiSubmitRecord custom records
5, set custcol on sales order lines that the lines are handled by this script.
6, nlapiSubmitRecord sales order

Problem
A user might update sales order/lines between steep 2 and steep 6. This sequence of updated should be handled as one database transaction or with proper optimistic concurrency control.

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 1 (Jan-Mar 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders