No worries, I totally understand.

You'll have to do that same thing on that output, where you do the sum, so it would be sum(map({427.Array},Hours)), typing in "Hours".

In the map function, type in "TaskID" (no quotes), don't map a value in, and the 425.taskID should be after the contains semicolon.

Ah I see, I forgot something. On the array filter after 425, change it to contains(map({424.Array};TaskID);taskID).

The hour one should be connected to the iterator right before it too, so 427 should connect to 425.   If that still doesn't work, can you show me an output array from the task array, and what task ID it was looking for?

I have run into this problem before, and the only workaround that I found was to surface the two fields when filling out the form, but then use a calculated field with if statements to use the secondary field selection, so you can say if({field A} = {Option 1}, {field 1}, if({field A} = {Option 2}, ...

The source module for the aggregators should be the iterator modules right before (the shaded region should go back to the iterator), it appears you have it set to the variable module. I think doing this will solve both problems, but I'm not 100% so if it doesn't solve the 2nd let me know.    

It's a little bit different, but here's how I would do it. On the project search pull in the list of tasks and hours, and on tasks pull in the revenue type, and on the hours pull in the entry date and the task ID.   Then, iterate thru the task list, filtering out any tasks that you don't want to kno...

Sorry, should have been more specific. I would create a variable, and do the calculation in there, and then you can map the variable where ever you need it to go.

In case that was confusing, I'll try to make it a bit clearer. On your project search, in the collections area, activate the map function and add allHours:hours. Adding that piece will cause Workfront to give you all of the hour entries on that project, and the hours portion also causes it to give y...