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!
NetSuite 2025.2 Release Notes - This document summarizes the changes to NetSuite between 2025.2 and the previous release.
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.
SuiteWorld October 6 - 9, 2025: Agenda Builder is live!
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Easy way to manage/swich connection strings/variables to different external systems?
Greetings,
We use our NetSuite Sandbox to interface with both/either our internal QA and Stage environments (while having separate Dev and Prod environments). We have some custom code that require different connection strings and keys for QA than for Stage. Current solution is a library config file and we just comment in/out variables for QA or Stage...but this is problematic as it's error-prone, not easy for non-technical users, and offers no easy visibility to which environment (Stage or QA) we're interfacing with.
Is there any functionality or process that would ease this? Ideally something a non-technical person could do, and that would be visible. Any suggestions or ideas on how others handle this are greatly appreciated.
0