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.
Confused by the log level behavior of nlapiLogExecution
I read the help and I understand the basic design of logging levels as they are used by several major logging frameworks. I'm confused about what I'm seeing in NetSuite though. I have a script which is logging at the AUDIT level (for auditing stuff) and the DEBUG level for, you guessed it! - debugging stuff.
My Script Deployment is set to Log Level DEBUG. When I change my Type filter to DEBUG on the Execution Log tab I don't see my AUDIT entries. I think of DEBUG as the highest log level or most verbose in which case I would expect to see DEBUG, AUDIT, ERROR and EMERGENCY. If I set the Type to Audit then I would expect to see AUDIT, ERROR and EMERGENCY. And on and on.
Steve Klett | Senior Developer
NetValue Technology