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.
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
24-hour Test Window to Help You Identify Required Changes to Your Production Account ?
The latest notice of this sort concerns the outbound single sign-on feature.
Ok, my real question revolves around what we can do when receiving a notice like this -- other than waiting and seeing(maybe) if something breaks. I appreciate the info that was in the email/notice but I'm looking for a little more guidance. Like, which integrations specifically raised the, I assume, automated flag that has put us in this group of potentially affected users. Or perhaps more info about how we can go searching for the issue in our instance.
I'd like to be more proactive and assured about our status after receiving these sorts of notices. Any help is appreciated. Thanks.
0