Issue: Automated collections based on a newly created metafield definition are not including products whose Boolean metafields (True/False) were set before the definition existed.
Context: An app writes Boolean metafields to products. After creating a metafield definition (a schema that enables consistent filtering/indexing across products), the user can filter collections by that metafield. However, only products updated after the definition seem to be recognized; earlier values aren’t being indexed into the automated collections (dynamic groupings based on rules).
Key question: Is this expected behavior, and is there a workaround to reindex or recognize previously set metafield values?
Status: No solutions or confirmations provided yet; the thread remains open and unresolved. No attachments or code are central to understanding.
We’re using an app that writes Boolean (True/False) metafields to our products. I’d like to set up automated collections based on those metafields. I’ve set up a metafield definition accordingly and now can filter my collections based on that. So far, so good.
However, products whose metafields were set before the metafield definition existed aren’t getting indexed in those collections.
Is this common behavior, and is there a workaround?