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.
NetSuite has launched SuiteSuccess Wholesale Distribution Edition, in Japan. Please join us the webinar on February 12 that introduces NetSuite solution with demos and case studies for Wholesale Industry.
Register Now
Have questions or experiences to share? Post your Release 2026.1 questions and join discussions in the Release 2026.1 category.
Intelligent Payment Automation, powered by BILL (formerly 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.
Pick Ticket (Advanced) Quantity Remaining and custom Item Field Columns
Hi all -
Anyone out there using Advanced PDF forms for a picking ticket? I got this working but suddenly two columns stopped working - one was a simple output of the qty remaining (left to pick) - I was using {item.quantityremaining} but as of a couple weeks ago that suddenly doesn't work any more (I have a support case and defect in with NetSuite but they are saying this is expected behavior).
The other field was to output a custom transaction column that simply sourced a field from the Item record (but didn't store the value). It's set in Printing Fields on my sales order form and was outputting, again, without issue until a couple weeks ago when it, too, suddenly stopped showing up. This one I know I could fix with a customization (likely script) that sets the value and stores it, and displays it on the form via screen fields, but it seems like overkill and I feel like I shouldn't have to.