<?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/4e5fa969b21043748414154c036cdd47&quot; frameborder=&quot;0&quot; width=&quot;1210&quot; height=&quot;907&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>907</height><width>1210</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>907</thumbnail_height><thumbnail_width>1210</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/4e5fa969b21043748414154c036cdd47-00001.gif</thumbnail_url><duration>81.87800000000001</duration><title>Workflow Rules and Mapping Custom Picklist Values</title><description>In this Loom, I discuss the issue I&apos;m facing with workflow rules and mapping custom picklist values between pipelines. I explain how I can map certain fields, but not custom picklist values, which results in empty values when records are created. I&apos;m seeking a solution to map custom picklist values from one pipeline to another using a workflow. Any insights or suggestions would be greatly appreciated.</description></oembed>