<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/418915d985834334bb214a6a0bfcb4d6&quot; frameborder=&quot;0&quot; width=&quot;1636&quot; height=&quot;1227&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1227</height><width>1636</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1227</thumbnail_height><thumbnail_width>1636</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/418915d985834334bb214a6a0bfcb4d6-f972944906110680.gif</thumbnail_url><duration>199.5496</duration><title>Optimizing Contextual Filters for Database Views 🔍</title><description>In this video, I discuss my current work within the Options Database and how it connects to the Consolidation and Facts databases. I&apos;m trying to group options by their associated consolidations, but I&apos;m encountering an issue where unrelated consolidations are appearing in my results. What I really need is a contextual filter that allows me to see only the consolidations linked to the current option I&apos;m viewing. If I can implement this filter, it would significantly enhance the relevance of the data I&apos;m working with. I&apos;m looking for insights or suggestions on how to achieve this contextual filtering across the databases.</description></oembed>