<?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/d8dd4e1a7eb844d4bf74e3a11f5457b1&quot; frameborder=&quot;0&quot; width=&quot;1664&quot; height=&quot;1248&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1248</height><width>1664</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1248</thumbnail_height><thumbnail_width>1664</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/d8dd4e1a7eb844d4bf74e3a11f5457b1-da5cd9419a127031.gif</thumbnail_url><duration>448.88</duration><title>Developing Ion Actions for ABOM Installations: Key Considerations 🔧</title><description>In this video, I discuss the key considerations for developing ion actions on ABOM installations, emphasizing the need to manage two IDs: the build requirement ID and the part inventory ID. I explain how to retrieve these IDs from the response after running a mutation, using an example where I installed a quantity of 1 onto an A-bomb. It&apos;s crucial to note that the part inventory ID may differ from what was initially passed in due to item splitting. I encourage you to install the GraphQL network inspector to better understand the underlying processes. Please ensure you have the correct IDs when developing your ion actions to validate against any ABOM installation.</description></oembed>