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.
Custom Project field is not triggering on Client "fieldChanged" function
Hi All,
I am currently facing an issue with a particular AP role. For the vendor bill, I have a Client Script that includes a fieldChanged function designed to auto-populate certain fields when the value of a specific custom project field in the VB changes. The script works as expected for most roles; however, it seems to be failing for a particular AP role.
The issue is that the fieldChanged function is not being triggered when the specific custom field in the vendor bill changes, although it works for other roles. I have confirmed that the user role has the necessary permissions to edit the field and execute the script. I also added 'alert' statements within the fieldChanged function to trace the flow of execution, but the alert is not popping up when the specific custom project field in the VB changes.