ZohoCRM Search Objects - Selecting incorrect items

I have a FastField form submitting data to this scenario:

The product lookup matches the FastField items from the array with the relevant items in Zoho. The “Zoho - Search Objects” filter only filters by Equals or Starts with.

The issue I’m facing is that the matching is not 100% accurate, in the example below I have selected “Fire Alarm - Chime” within FastForm, but when it does a lookup it comes back with the wrong item. Here it came back with “Fire Alarm - Chime/Strobe”.

This seems to happen a lot and can’t find a way to do an exact match.

Hi Max.

I believe you did a great job, but your scenario is still a bit off.

Are you doing anything special in the Format Data modules, based on the part name?

If you are, just put the filter after the iterator.

But If not, then why do you even need the filters and 3 branches?

You could probably do it sequentially, without having to wait for the variables.

The only issue I see is that you are using a mapping that seems to be broken.

Since lookupFA_Desc is an array of a single element, just reference it by lookupFA_Desc[1]

@damato

Hi there, thanks for taking the time to review.

In response to your suggestions:


01 - The Format Data looks like this:

I need to structure in a way that ZohoCRM requires. And then I comma separate each item.


02 - The multi branches are used as the FF form has “sub-forms” e.g Fire Alarms, and in each there will be an array of data for each item. So I figured I’d need multiple branches to process each sub-form group.


03 - Here’s a look at the filter:

It does work in its current state, and ran a few tests this morning.

Barring those suggestions, I still need to figure out how to make it choose the correct items, it feels like it selects the last item from a given set of names:

Item A
Item A - Type B
Item A - Type C

Here it would select: Item A - Type C as its the last item. When in fact the item should have selected Item A.

Hi Max.

From Format Data config, I can see that you don’t need different routes for different elements, since you don’t seem to be applying a different aggregation structure for each type of element (Fire Alarm/Fire Sprinkler etc.).

I can’t help very much without seeing what the filters before the iterators contain, but I still believe that you only need one route and also that you should specify index 1 for the lookupFA_Desc[] array.

Borrowing from the Zen of Python:

Explicit is better than implicit.

And if you do need multiple routes, you can put only one iterator before the router and apply the filters after the router.

@damato