MatchingAlgorithm acting weird

Hi all!

In my B2B marketplace, I have a feature that matches a ‘buyer’ with their desired product from a ‘seller’ posted product based on the data field ‘numbers’ a buyer provides through the input fields “Text (Numbers only)”. The value store here goes directly to a database called “BuyerPreferences”. Here’s an image:

Now in backend workflows, it gets a little messy & tricky. I am posting screenshots of the backend workflow API I created:

Action (Step 1) inside it:

With these settings, it works smoothly but it searches directly for the value instead of between the minimum and maximum values.

With these settings, it doesn’t work as it doesn’t create any notification in the backend. But I want it to collect minimum and maximum values for “Creating a Notification”

Another API [For creating a notification of the first API]:

Action (Step 1) inside it:

This is where this API triggers on the front-end workflows (Create a Product page):

Please help me out with this problem, I want my API to run between the minimum and maximum values of a buyer’s preferences, so if a product has a value in between the buyer-specified minimum and maximum values, it should create a notification in the backend.

Shouldn’t you be using parameters such as >= or <= ?
Less than or Equal to
Greater than or Equal to

I tried that, but it didn’t work that way too.

If I provide a single value of core, diameter rather than min and max, it works then.

Are you trying to match ALL the criteria at the same time?

It had to do something with the parameters, I just changed the parameters as @ hi.luisacosta told me to, and it worked after a lot of live debugging with him thanks, sir!

This topic was automatically closed after 70 days. New replies are no longer allowed.