<?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/1e2239f4a80b4e088bc5dd59f15b299b&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/1e2239f4a80b4e088bc5dd59f15b299b-80a06796fc0f0767.gif</thumbnail_url><duration>87.784</duration><title>Troubleshooting Custom Input Issues in the Transform Datastep 🔧</title><description>In this video, I&apos;m addressing an issue I&apos;m experiencing while running the transform datastep, specifically with a custom input that keeps getting deselected. I demonstrate this problem by adding a custom input and running it, only to find that it doesn&apos;t retain my selection. This is frustrating, as I need to keep my custom input intact for the task at hand. I&apos;m reaching out for any insights or solutions to resolve this issue. Please let me know if you have any suggestions!</description></oembed>