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
Project summary tasks after all children/work tasks are deleted
It is possible to create the following multi-level project WBS, so long as each of the summary tasks is entered as a Milestone rather than Task.
Once a work task is added to a summary task, the summary task and all of its parents are no longer marked as milestones.
The Work 1.1.1 task can be changed to have Summary 1.2 as its parent.
However, after doing that, I cannot create a new work task that has Summary 1.1 as its parent.
The appears to be caused by Summary 1.1 no longer being a milestone AND not having any children tasks. It also still has the last computed value for Planned Work in the record. As a work-around, Summary 1.1 was changed back to milestone by editing it and saving it after setting the Planned Work field to zero and clicking OK at the prompt.