Event name in notification record is incorrect after moving an Notification Record through update setIssue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms When trying to move a Notification Record to a different environment via update set, the event name is not showing correctly and defaulting to the first selection in the dropdown list. The preview of the update set also does not catch this non-existing event name. Release All Releases Cause Since the "event name" is a string field and not a reference field, the update set preview will not detect an error. If the event name registry record does not get moved over in the update set, the event name field will automatically default to the first selection in the dropdown list. If you check the XML for the notification record, you will see the correct event name, but the dropdown selections for that field on the notification record will not exist. Resolution When moving notification records via through update set, be sure to also move the event registry record in the update set as well.