Can we duplicate the back end process that makes the Unsubscribe field durable for use on other fields? Not specifically asking if the Unsubscribe data can be updated to other fields, but if the technology that does that process can be used to update other fields.
User case: My organization has intentional duplicates. Field A on Record A is updated. We would then want Field A on intentional duplicate Record B to be updated.