Can you bulk update Predecessors in Projects?

[DanaLa3]

I am looking for tips and best practices on how Project Owners can update predecessors on their Projects without using fusion. We only have one resource with fusion experience so that would be a longer term solve for us.  Our users can have projects between 400-1000 tasks that are often updated and tweaked to add more templates etc. I haven't found a way you can bulk update predecessors, but I've offered users a way to bulk update statuses, priorities and approval paths. I'm also using approval paths whenever possible to avoid the need to add more tasks for re-work.  It's becoming very labor intensive for these project owners so any insight would be appreciated. 

Thanks

[skyehansen]

Perhaps stating the obvious here -- if you're adding another project template to a project with 400-1000 tasks, there are sections that you can fill out during the addition process that help you set predecessors and parent tasks.

Can you maybe clarify WHY there's a need to "bulk update" predecessors? Are the additional templates being pulled in by fusion? Or when are the predecessors needing to be updated?

[DanaLa3]

Thanks for responding. We have lots of mini templates that would get added to existing projects so updating predecessors if a regular thing with our setup. For example you may need to insert a 3 task template into an existing project so updating predecessors is necessary especially if it's in the middle of a set of tasks. It's how we are able to route work back to our partner teams. Adoption of approval paths hasn't been great, so this is our way to route work back to teams for revisions. We don't have any fusion scenarios where we are adding in template tasks. 

[kautuk_sahni]

@DanaLa3 Just checking in — were you able to resolve your issue? We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!

[DanaLa3]

No immediate solves just yet. We have a unique type of setup but it looks like we are aiming towards using approval paths and if that is the case then updating predecessors will not be much of an issue.