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
saleUnit, stockUnit and purchaseUnit
NetSuite case 597301:
In tests, it appears that saleUnit, stockUnit and purchaseUnit can only be updated via web services if these values are blank.
Stated another way, if there are values in saleUnit, stockUnit and purchaseUnit, they cannot be changed via web services.
To some extent, it makes sense because when you change the values via the UI, you get a user prompt which web services cannot press ok to.
That said, I would think an error in the xml response would be appropriate.
Can anyone confirm the behavior?
0