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.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
Season’s greetings to you and yours! As we head into the holidays (December 24 – January 4), we want to take a moment to celebrate the incredible strength and collaboration within our community. Even during the break, you can continue to benefit from connecting with peers, searching related threads, posting your questions, and marking helpful replies as “Accepted” in the Support Community.
Please note our dedicated team will be on reduced coverage during this time, and regular responsiveness will resume on January 5. Wishing you a joyful and restful holiday season!
-The NetSuite Support Community Team
Is there a limit for Scheduled Workflows?
I have a workflow based on a Contact Saved Search.
The saved search returns 1700.
My workflow State Condition is Tax Notification = False.
There were only 300+ contacts where the Tax Notification field is False.
I could not get the workflow to fire.
I changed the Contact Saved Search to only return the 300+ contacts where the Tax Notification field is False. (I know the saved search should have limited the results in the first place)
This was the only change I made.
The workflow fired and updated the 300+ contact records as expected.
My Question ... just for information: ... Do workflows to update a record field have a Saved Search row limitation? (I know it is more efficient to reduce the pool/saved search in the first place). I just spent too much time, replicating & troubleshooting a Workflow from one that worked perfect. Since the only difference is a criteria to reduce the saved search results the workflow uses as a condition, I was wondering.