<?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/cc332f43f68342efb10b35764bf866b3&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/cc332f43f68342efb10b35764bf866b3-cc40822db244edf7.gif</thumbnail_url><duration>191.152</duration><title>Demo: Persisted Block Props Metadata Import</title><description>This Loom demos persisting imported Obsidian sync metadata into page block props using the page UID. The author starts by retrieving the page UID and confirming there are no existing block props, then emulates an import by creating a demo node, obtaining an RID and identity via the PR’s import functions, and writing the imported source identity to a Rome page. When the page is pulled again, block props are present, reflecting the imported discourse graph data. They add blocks and note the metadata remains persisted after editing content, while mentioning a potential conflict seen on another page with the same UID that appeared as a false positive.</description></oembed>