Change Details

Newer CID 5273764 opt-in; Older CID 952021 opt-out. After the merge, Civi saved the newer CID into the oldest as an opt-out instead of adjusting it to reflect what was attached to the newer CID. At the moment this change isn’t reflected at Acoustic, however, tomorrow it will be. **CIDs examples not yet merged: ** Newer CID 60089976 opt-in Older CID 143328 = After the merge Civi will save the newer CID as opt-out instead of keeping the option from the recent CID Newer Contact ID: 60084551 opt-in Older CID 134613 = After the merge Civi will save the newer CID as opt-out instead of keeping the option from the recent CID It is not scalable to manually remove the opt-out tags from Civi after each merge that saves the incorrect option, and the deduper interface doesn’t show us when an email merged was incorrectly saved as opt-out. Can the overwrite or a mechanism be implemented to prioritize the option from the latest CID over the older one? {F37641107}

Newer CID 5273764 opt-in; Older CID 952021 opt-out. After the merge, Civi saved the newer CID into the oldest as an opt-out instead of adjusting it to reflect what was attached to the newer CID. At the moment this change isn’t reflected at Acoustic, however, tomorrow it will be. **CIDs examples not yet merged: ** * Newer CID 60089976 opt-in Older CID 143328 = After the merge Civi will save the newer CID as opt-out instead of keeping the option from the recent CID * Newer Contact ID: 60084551 opt-in Older CID 134613 = After the merge Civi will save the newer CID as opt-out instead of keeping the option from the recent CID It is not scalable to manually remove the opt-out tags from Civi after each merge that saves the incorrect option, and the deduper interface doesn’t show us when an email merged was incorrectly saved as opt-out. Can the overwrite or a mechanism be implemented to prioritize the option from the latest CID over the older one? {F37641107}

Newer CID 5273764 opt-in; Older CID 952021 opt-out. After the merge, Civi saved the newer CID into the oldest as an opt-out instead of adjusting it to reflect what was attached to the newer CID. At the moment this change isn’t reflected at Acoustic, however, tomorrow it will be. **CIDs examples not yet merged: ** * Newer CID 60089976 opt-in Older CID 143328 = After the merge Civi will save the newer CID as opt-out instead of keeping the option from the recent CID Newer Contact ID: 60084551 opt-in Older CID 134613 = After the merge Civi will save the newer CID as opt-out instead of keeping the option from the recent CID * Newer Contact ID: 60084551 opt-in Older CID 134613 = After the merge Civi will save the newer CID as opt-out instead of keeping the option from the recent CID It is not scalable to manually remove the opt-out tags from Civi after each merge that saves the incorrect option, and the deduper interface doesn’t show us when an email merged was incorrectly saved as opt-out. Can the overwrite or a mechanism be implemented to prioritize the option from the latest CID over the older one? {F37641107}