[Suspected Bug] Creating a Smart Collection filtered by metafield

Retired Boards Appdev Merchandising
1

I found what seems to be a bug while creating a Smart Collection via the Rest API to filter by product metafields.

I pass in the condition_object_id value as a number, but when I request it, I see it’s saved as a string, which breaks the functionality (see images below).

condition_object_id should not be a string, and I never passed it in as a string
condition_object_id should not be a string, and I never passed it in as a string614×614 11.6 KB

As you can see in the 2nd image, it breaks the page's functionality in two ways
As you can see in the 2nd image, it breaks the page's functionality in two ways647×781 32 KB

As you can see in the frontend image, it breaks the page’s functionality in two ways:

  1. It can’t render the rule
  2. The rule isn’t functional

However, when I reconfigure the collection from the frontend, the API returns condition_object_id as a number, and everything works.

This leads to me believe that it’s a rest API issue, being that’s how the bug is reproducible (and the frontend doesn’t use it).

2

Hi Menachems,

I’ve flagged with to our API support team to investigate - will report back asap!

1 Like
3

Hi again Menachems,

Just to update - our team has confirmed this is a bug on our side and are working on a fix.

1 Like