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.
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.
Checkbox field values inconsistent
I'm noticing that custom field types that are checkboxes are inconsistent in terms of how they accept or read values:
For example, on a custom record, if I have a custom field "custrecord_mycheckbox" setup as a checkbox, then 2.0 says I must set this (and assume read) as a boolean:
record.setValue({fieldId: "custrecord_mycheckbox", value: true});
and
record.getValue({fieldId: "custrecord_mycheckbox"}); returns true or false
If I attempt to do set this using 'T' or 'F' like with 1.0 methods, I get this error:
You have entered an Invalid Field Value T for the following field: custrecord_mycheckbox
However, if I add a dynamic field in beforeLoad to the record "custpage_mycheckbox" and type it as a checkbox, and I try and set the defaultValue using boolean, I get this error: