<?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/44ef0e3c7bdc4053a2ac95f66a809019&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/44ef0e3c7bdc4053a2ac95f66a809019-ea19ea2d98c57663.gif</thumbnail_url><duration>228.774</duration><title>Finalizing Cost Integration and Troubleshooting Issues 🔧</title><description>In this video, I walk through the final steps of integrating costs from our first table into the new table, highlighting a couple of issues I encountered along the way. I found that while testing, the system successfully pulled in details for 76 rows, but it stopped processing when it hit an item not present in the new table. I need to ensure that the process continues even when an item doesn&apos;t match, so I&apos;m looking for guidance on how to adjust that logic. Please review the steps I took and let me know how we can resolve this issue to keep everything moving smoothly.</description></oembed>