Discussions
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
Intelligent Payment Automation, powered by BILL (aka Bill.com), lets you automate payments, manage vendor details, and bank account information within NetSuite.
The SuiteApp is available to organizations based in the U.S. with a valid U.S. address, or to global customers (except Canada, China, and Japan) with U.S. business subsidiaries. It only supports payments to vendors operating in the United States.
For more information, visit this thread.
Scheduled Script concurrency control?
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.