<?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/b53a16e419e640199fb11140af67d20d&quot; frameborder=&quot;0&quot; width=&quot;2560&quot; height=&quot;1920&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1920</height><width>2560</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1920</thumbnail_height><thumbnail_width>2560</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/b53a16e419e640199fb11140af67d20d-74de324b9db75a0c.gif</thumbnail_url><duration>207.8803</duration><title>Conditional Rules &amp;amp; Record Actions</title><description>In this video, I demonstrate two methods to set conditional rules for field values in a database table. The first method involves setting conditions directly on the value field, which limits flexibility and editability. I then recommend using record rules instead for better flexibility and control over field values. By applying record rules based on the yes-no field, you can dynamically update the value field without hard-coding values. I showcase how this approach allows for easy value modifications and avoids system-wide updates. No action is requested from the viewers in this video.</description></oembed>