Global delete contact preferences / consent module records
If I do an import with a mistake - eg: wrong version of the privacy statement, I can add the consent again, but I need to manually delete the ones that were imported incorrectly. For example, i got a consent statement trimmed due to a comma - I can fix that and add them again, however, I'll need to manually delete the incorrect ones. If the mistake is on 1000s, we would either manually delete or the consent module will become messy with complete and incomplete records.
-
Graziela Baia
- Jun 1 2018
I would really like to be able to delete consent for the similar reasons. I was asked to add a consent based on a signed registration form, but I didn't add the consent and privacy statement.
this is really needed. it shouldn't have been implement alongside the consent table. a really big oversite.
Same here, we urgently need this "global delete specific consents functionality" as well! Especially because these constituent won't receive emails anylonger at the moment, terrible for all our fundraising projects!
We have over 40,000 consents which were added without an opt in or opt out option which need to be removed. It is crazy to comprehend deleting all these manually! We urgently need this consent deletion functionality.
I'm guessing this was never implimented
I made a mistake on importing hundreds of consents and need to correct the mistake. This functionality would be very helpful!
I'd vote for Global Change and Global Delete.
There should be a way to bulk delete consents in case it was imported in error, as this is quite a common case.
+1
Really, if a record type is added, all of the related admin functionality (mass insert, mass update, mass delete) ought to be as well. Kind of silly to require people to file an "idea" to be drip fed what should be standard functionality...
same as others, the problem is we cannot update current consent with import, just add. so we should have the option to update the current consent, or the option to delete duplicates and retain the most recent, or both...
We are using importomatic to upload bulk consents, and because of the granularity of our preference forms we end up with quite a lot of duplicate consent records where the supporter has not specified a communication type. Therefore it's really important that we identify those and are able to globally delete them.
This would definitely be a more efficient way to use my time. Just makes things easier
I completely agree. It's been a nightmare not being able to globally delete in this scenario.
Of course this is needed. How else can consent be managed