Context Aware integration field implementation

Developing with Prismic
1

Hi Prismic Community,

We're building an e-commerce site with Medusa.js backend and Prismic for layout management. We have a challenge with Integration Fields that we'd love input on.

Our Goal: When designers create collection page layouts, they should only see products from that specific collection in Integration Fields dropdowns.

Current Problem: Integration Fields show ALL products globally, but we need collection-specific filtering.

What We've Considered:

1. Client-side filtering (works but poor UX - designers see irrelevant products)

2. Push Data with dynamic catalogs (complex, race conditions, doesn't scale)

3. Multiple static catalogs (manual setup per collection)

Ideal Solution: Integration Fields that can receive context from the document being edited (e.g., if editing a "Summer Collection Layout", only show summer products).

Questions:

- Is there a way to pass document context to Integration Fields?

- Are there any upcoming features for contextual/conditional Integration Fields?

- What approaches have others used for collection-specific product selection?

- Any alternative architectures you'd recommend?

Thanks for any insights! :folded_hands:

2

hey @Isai_Gonzalez_Olmos , right now here isn’t a way to filter an Integration Field catalog dynamically based on the context of the context.

The only way to achieve something close would be to create separate catalogs and assign them to specific page types. From there, you could use Spaces to control which people have access to those page types (: