Issue with Matching Custom Field Values Between List A and List B in Clickup

Hey, we have a problem matching the value of a custom field with the date field from List A to the same custom field on List B. Tasks should be assigned values based on the Task Name.

Unfortunately, I’m not sure how to aggregate this data. When I grouped operations in the aggregator by Task Name, they were duplicated, which we want to avoid.

Could we ask for your help?
FAKTURY OBSŁUGI DZIAŁA.json (197.0 KB)

Hi @Vinseo, Why are you aggregating the data from watch tasks ? Can you show an example output of watch tasks ? Does it generate multiple bundles ?

One more thing : you don’t have any filter between modules, how do you think you’re gonna MATCH one data with another ? I think you need a filter between list & edit modules.

As for aggregating data, what’s the requirement ? Do we aggregate each column ? like :

task in A :
name = abcdef
sales = 150

task in B :
name = abcdef
sales = 250

What do we do ? do we aggregate 150250, 500, keep 250, keep 150 ? You can configure all this choices in Edit module.

It works exactly like this.
Watch Task retrieves tasks from List A, Array Aggregator collects values from the custom field, and List All Tasks fetches tasks from List B. And here comes the problem—while Edit a Task with Custom Fields does overwrite the custom fields, it always sets today’s date instead of the one from List A. Unless I group in the Array Aggregator by Task Name—then everything works correctly, but it consumes a large number of operations, which I want to avoid.


@Vinseo,

Why is array aggregator ‘collecting values’ ? Aren’t they already available for future reference ? What is the purpose of this aggregator ?

You still didn’t explain how do we match tasks A with tasks B.

Could you also show Edit task module config?

Unfortunately, they are not, which is why I had to use something to collect this data.

I previously linked the tasks using a filter with Task Name = KEY (from aggregator).

Tasks from List A are supposed to overwrite a field in tasks from List B.


@Vinseo, If array aggregator is necessary, you’ll have to use iterator afterwards on this array to correctly go through all results. Else you’re just comparing first element of the array each time and 2nd and 3rd values here are ignored.

You said the problem was that it put today’s date for all tasks that it found. Yes, it’ll be the case, because Array aggregator is not iterating in all of the dates it found in ‘watch’ module. Unfortunately for this use case you’ll have to consume operations. If your filter is correct between list and edit modules, you’ll only consume 1+1+1 operations for each task found in watch tasks.

Neveremind, data from Watch task can be placed in Edit Task, my bad.
The problem is that for each action, it again consumes a large number of operations. Is there any way to limit this?

@Vinseo, You basically need 3 modules : watch, list, and edit. for 1 task watched it’ll consume 1 list task, and assuming you only have 1 match (taskname A = taskname B), edit should only be executed one time. This results in 3 operations per watched task. Does it consume more than that? We can’t have less.

Watch Tasks performs a single operation and retrieves all tasks from List A. That part works fine.
However, List All Tasks consumes an operation for each task, even though it already has all the necessary data from List B in a single operation.

I’m not sure what to add to make List All Tasks complete in just one operation. I probably need to add a module, but I don’t know which one.

When I use only three modules—Watch Tasks, List Tasks,and Edit Tasks—the last two multiply the number of operations. If List B has 50 tasks, the number of operations in Edit Task increases to 2500. There must be a way to optimize this. :cry:

@Vinseo, Please screenshot the filter between list and edit modules. Edit should only be executed once if your filter is correctly set up and even if list B has 50 tasks.

@Vinseo, please remove the aggregator. only use 3 modules. keep the filter, but reference task name from list all tasks instead.

if you still have more operations on ‘edit’ than you have on ‘list all tasks’, please post screen of your filter results. your filter should guarantee that it only passes to edit if conditions are satisfied.

1 Like

Everything works thanks to filters, but unfortunately, List All Tasks still executes operations based on the number of tasks, even though all the necessary data is available in a single operation.

In Edit, there is only one operation because I set conditions to allow only one to pass. That part works fine.



@Vinseo, Yes I forgot to mention that part. I don’t think it’s possible to do all this in less operations. At most, you can do it in MORE operations, but in LESS TIME. I don’t think that’d be interesting for you.

Edit : if you REALLY want to optimize this and do operations in bulk, you’ll have to look in API calls and bulk update (if available in documentation).

Ok, then I’ll leave it as it is for now. Thank you very much for your help :slight_smile:

1 Like