<?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/b391b33f651a4788b24e0e98dd4214d8&quot; frameborder=&quot;0&quot; width=&quot;1662&quot; height=&quot;1246&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1246</height><width>1662</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1246</thumbnail_height><thumbnail_width>1662</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/b391b33f651a4788b24e0e98dd4214d8-7bc4461573b15f2f.gif</thumbnail_url><duration>270.247</duration><title>Generic Route for Triple Graph Upsert</title><description>This Loom explains a new generic route for posting and upserting a complex triple graph JSON payload. The author notes the input format is more absurd than expected and assumes valid JSON for now, with a validator planned for a future PR. The logic fetches the current user account ID, validates and converts node content including date handling, and then upserts nodes and relations while ensuring relation triples have the needed relation type and source and destination schemas. To support cross-app results, the route builds node schema and relation type schema sets, fetches missing schemas from the database, maps local IDs to cross-app objects, and includes an assert and an observed test for cross-app data with embeddings and relations.</description></oembed>