<?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/f0782e474264412d8e887b4b75f9f8f6&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/f0782e474264412d8e887b4b75f9f8f6-3f4594190484eaad.gif</thumbnail_url><duration>575.706</duration><title>Understanding DXT Variables and Affiliations in Athenian Console</title><description>In this video, I demonstrate how the as-of-date functionality in the supporting documents model impacts the affiliations root collection within the DXT variables list in the Athenian console developer tool. We start by assembling the DXT collections and reviewing the data for four directors, noting their active and inactive statuses. I then show how applying an asset date, specifically June 20th, filters the affiliations collection to reflect only relevant data, resulting in three records instead of four. This highlights the importance of including an asset date when generating documents like registers and ledgers. I encourage you to apply this knowledge in your future document generation tasks.</description></oembed>