Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
V2007.1: Change in default for "Credit Card Approved"
After the 2007.1 upgrade, all of our transactions (sent through a 3rd party processor in our web app) are coming in through the API as "Unapproved".
It turns out that we had not been setting this value in the transaction, and that the default value changed from "True" to "False". I do recall that in prior versions the default had in fact been "False", but this seems to have first changed in 2007.0.
The question is: this is *not* documented anywhere in the upgrade docs, either the release notes or bug fixes. How can we build a reliable web app integrating with Netsuite when their API rules change without being documented?
0