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.
Please use a personal profile, not an anonymous one...
Community guidelines write:
We are a community of amazing people who want to get know each other and create connections. Represent yourself authentically and provide as much information about yourself as you can in your profile. Include a photo of yourself. We all prefer to interact with human beings rather than flowers, cars, and bouncing ball avatars.
Some ideas exist on this: