Creating tasks through Fusion with planned hours and no assignment | Community
Skip to main content
Level 2
July 9, 2026
Solved

Creating tasks through Fusion with planned hours and no assignment

  • July 9, 2026
  • 7 replies
  • 115 views

Hi all!

 

I’ve created several Fusion scenarios to create tasks based on a cadence and while everything is working as expected, the only portion I can’t figure out is adding planned hours to each of the tasks.

 

I have a project I use to store the tasks and their planned hours and right before the create tasks module I have a search module to go through that project and match the task name and output the planned hours (work required), but when I map the planned hours section in the create task module the planned hours don’t get added.

 

For context the tasks are being created on a Simple duration type with a Fixed Dates constraint and are initially unassigned.

 

Any ideas? Thanks in advance!

Best answer by CamiD

Hi ​@KristenS_WF ​@trish_7210! Just got a response from the ticket. I’ve tested out and it worked for me. Here's their response:

First, you do want to be updating Work instead of Planned Hours, but that alone won't always work. There is a field called 'isWorkRequiredLocked' in the API and it shows up in the module as 'workedLocked' and you will want to set that value to True. 

This forces that work value that you are entering to be input. It's needed because various factors can sometimes override the work field when a task is created via the API (project dates, task constraints, and other task values), so you need to lock the work value when entering it.

 

Hope it works for you too!

7 replies

KristenS_WF
Level 7
July 10, 2026

I know in the past (when I was using Fusion to bulk update the planned hours for several tasks) I needed to use the ‘Work’ field rather than the ‘Planned Hours’ field.

However, I tried this in a test scenario just now, and the hours are not getting updated.  I tried using both a Create a Record module to create a new task and an Update a Record module to update an existing task--neither updated (I also tried adjusting the task duration, and that failed as well).  I’d suggest filing a support ticket to check if there is a bug.

CamiDAuthor
Level 2
July 10, 2026

Hi ​@KristenS_WF thank you so much for your response! Knowing it’s happening to other people as well, I’ll definitely log a support ticket and get back here with the solution.

 

Thanks again! 

Level 2
July 14, 2026

I’m having a similar problem, so I’d love to know what you find out. In my case I’m trying to take the actual hours from a completed project and apply them as the planned hours for a new project. Same outcome though, I run the scenario fine, but the planned hours don’t update. Have you recieved an answer on your support ticket?

CamiDAuthor
Level 2
July 14, 2026

They’re still investigating it, I’ll be sure to come back when there’s a resolution.

CamiDAuthorAccepted solution
Level 2
July 14, 2026

Hi ​@KristenS_WF ​@trish_7210! Just got a response from the ticket. I’ve tested out and it worked for me. Here's their response:

First, you do want to be updating Work instead of Planned Hours, but that alone won't always work. There is a field called 'isWorkRequiredLocked' in the API and it shows up in the module as 'workedLocked' and you will want to set that value to True. 

This forces that work value that you are entering to be input. It's needed because various factors can sometimes override the work field when a task is created via the API (project dates, task constraints, and other task values), so you need to lock the work value when entering it.

 

Hope it works for you too!

KristenS_WF
Level 7
July 15, 2026

Thanks!  That field’s new to me.  Looks like there’s a corresponding one for Duration as well.

Level 2
July 15, 2026

Thanks ​@CamiD - I’ll try this.