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.
Intelligent Payment Automation, powered by BILL (aka 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.
Changing preferred form affects WSDL updates
I am using the NetSuite WSDL to update customers on a regular basis from an outside database. This has been working flawlessly for weeks. Today, our staff set a custom form to be the preferred form. This form does not have the fields that I am updating on it. At the same time, my update program began throwing errors, stating that I was unauthorized to update a certain field (custentity40).
We changed the preferred form back, but I think this is a serious flaw. The WSDL isn't using a form, so why is it bound to what is available on the form? I am also running the update program as a NetSuite admin, so I have full access to everything, yet, I get a message that I am unauthorized to perform the action.