lrooney - This is not definitely not how we intended for Consent records to be used. They are expected to be a running, comprehensive history of opt-ins and opt-outs for a donor, including multiple elections for the same Channel/Category over time. The entire reason they tie to (trigger) Solicit Code assignments is to give you an easy way to see the “Current State) of their communication preferences.

I would recoccomend changing your current process to leave “old Consent” records as is and look for Solicit Codes to track how many people are currently opted in vs not. 

When someone updates their consent we record the change as an action, delete the consent record and add a new one so it would be much easier if we could just update the existing consent record. We only want each person to have one consent record per channel as it was messing up queries when we were trying to report on how many people had opted-in / -out of a particular channel, they were appearing in results even if it is an "old" consent record.

Hey David,

Thanks so much for submitting this idea. I wanted to point out that the lack of an Edit option for Consent was intentional. In may cases these records are used as an "audit trail" and we didn't wan them to be easily edited in fear that any external audit might consider the trail insufficient if the historical records could be edited on a whim.

We certainly didn't intend to punish users for data entry mistakes, but there is a fine line between making it easy and making it "too easy".

Thanks,

Jarod Bonino

Senior Product Manager, Raiser's Edge