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.
Socket Mobile Scanner isn't identifying the barcode with the item
I created an "additional upc" field on the custom tab of items since we have many items with more than one barcode. I then added it to SCIS Website Setup record in the Search Index and as a Field Set for Search.
This enabled the data in that new field to be searchable when I type in a scan code into Global Search and SCIS search.
However, our barcode scanners (Socket Mobile) aren’t working with this new field. I can see the scanner read the number correctly, but it can’t associate it with a product. It just says “The following barcodes were not found. Please re-scan or search for the items”. This exact error led me to SuiteAnswer 63935, and I followed it’s direction but the scanner was already configured the way it directed. And, of course, the scanners work with data that’s in the upc field; so I know they work, it's just something wrong with my custom field.