<?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/95940c63478049d08a0e36920f6a2a3a&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/95940c63478049d08a0e36920f6a2a3a-a6ad0870c49de283.gif</thumbnail_url><duration>90.208</duration><title>Day 21 - Excel - 03 Outline</title><description>This Loom outlines the plan for exporting element data from Rabid to an Excel “smuggler” workflow. It covers getting elements, reading element data, preparing the export as nested lists where each inner list is a row, and generating an Excel file path that includes a timestamp. After exporting, it suggests reporting the same data back inside Rabid using tables for debugging and user visibility, and exporting element IDs to relate imported data back to the correct element. As a bonus, it also plans to read the exported Excel file and import the data back into Rabid with the element relationships intact.</description></oembed>