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!
Update your Profile with your Support type to get your Support Type badge.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
noautoassignlocation field set for Sales Orders created in SCA
Hello,
We are on the Kilimanjaro version of SCA and we're having an issue with Sales Order line item location not being set correctly when a customer completes check out. We currently use ALA to manage setting locations on SOs. However, any SO that's created on store checkout has the 'Do Not Auto Assign Location' field (noautoassignlocation) checked on the line items, which we believe bypasses ALA, and the location never gets updated from the default value when our ALA runs.
These are the values set when an SO is created from store checkout:
These are the values that are set when an SO is created from the UI:
0