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
NetSuite Admin Tips | Common mistake new Administrators make when setting a Condition in a Workflow
Administrators who are new to NetSuite make this common mistake when setting a Condition using SuiteFlow's Visual Builder.
The scenario here is when the admin intends to check the value of a field in the Workflow Base Record (The record type the workflow is set to run on).
Novice admins tend to also set the First Column (Record) to a field named after the base record that instructs the workflow to look up the field in another record joined by the selected field in that column, not in the base record which is not the intended behavior. Therefore, it baffles them why the condition didn't work.
----------------------------------------------------------------
1