It is really important that I am able to export consent fields. In query, you cannot query for the most recent consent, so I need to be able to export all consent fields. We discovered that our "Enable Consent Tracking" was not checked and therefore I need to do a mass change to clean up records where the consent did not map to a solicit code.
We are implementing Emma and beginning the process of mapping preferences to consents. This would be helpful for analysis and for creating integrity reports.
We're about to start mapping email information from Mailchimp to the consent fields in NXT and this would be extremely helpful - doesn't feel like it should be too difficult to implement.
Please let us know when consents can be exported. I understand issues can arise with newer modules, but some feedback would be nice. Can we at least know if this will ever be possible? It will help with planning ahead.
I don't understand why consent can be queried on, but not exported. Please introduce this to export- I was very surprised to find that it wasn't there, and am now having to do a number of work arounds to gather this information in a concise manner.
We have a current issue raised with support that consents are not being applied via online express for all records. I'm flabbergasted to discover that I cannot export a consent history to audit and find records where this is the case.
I would like this to be able to do data cleaning. The consent records can be deleted individually in both web and database views so there is no audit reason that is valid for not having this. An import went bad and it would have been useful to export and update with the correct data.
It's strange that I can pull this info from Query but not Export. We use Consents now for email sign-ups, in some of our analytics I'm asked the date someone subscribed--which should be easy enough based on consent date. It's frustrating that I need to export from query & combine excel files to get the data in one report.
This seems really important. I realise the solicit codes work with it, but that doesn't help in terms of auditing the consents themselves, and when/how they were made.
We need to be able to export consents using the export module but this seems impossible currently as the Export module allows only Solicit Codes to be exported.
Is there a plan to add a feature that allows the export of all constituent contact consents? This is a critical requirement to ensure GDPR compliance and mailing/email status are always accurate ahead of supporter communications. Strange that it wasn't included as an option from the introduction of the consent tab.
The Consent Button is an improvement on the previous Attribute method for storing/tracing Consents, but you definitely need to be able to Export the Consents. Furthermore you need to be able to Global Add/Delete/Change/Replace on Consents too, seems odd you can do it on a manual basis but not globally - not great for database housekeeping.
Feels silly that this is not an option already
It is really important that I am able to export consent fields. In query, you cannot query for the most recent consent, so I need to be able to export all consent fields. We discovered that our "Enable Consent Tracking" was not checked and therefore I need to do a mass change to clean up records where the consent did not map to a solicit code.
We are implementing Emma and beginning the process of mapping preferences to consents. This would be helpful for analysis and for creating integrity reports.
We're about to start mapping email information from Mailchimp to the consent fields in NXT and this would be extremely helpful - doesn't feel like it should be too difficult to implement.
I can't believe that this idea was posted in 2018. Please of pleae implenent this Blackbaud!
We kindly request that BB figure out how to make this possible. It really limits its functionality for our uses.
This would be so useful
Please let us know when consents can be exported. I understand issues can arise with newer modules, but some feedback would be nice. Can we at least know if this will ever be possible? It will help with planning ahead.
I don't understand why consent can be queried on, but not exported. Please introduce this to export- I was very surprised to find that it wasn't there, and am now having to do a number of work arounds to gather this information in a concise manner.
We have a current issue raised with support that consents are not being applied via online express for all records. I'm flabbergasted to discover that I cannot export a consent history to audit and find records where this is the case.
Please allow Consent records to be exported.
I find that i need to export the latest consent date along side the solcit code. It would be really useful to have this to query on and export.
I would like this to be able to do data cleaning. The consent records can be deleted individually in both web and database views so there is no audit reason that is valid for not having this. An import went bad and it would have been useful to export and update with the correct data.
It would be nice to know when this feature will be available for use.
It's strange that I can pull this info from Query but not Export. We use Consents now for email sign-ups, in some of our analytics I'm asked the date someone subscribed--which should be easy enough based on consent date. It's frustrating that I need to export from query & combine excel files to get the data in one report.
This seems really important. I realise the solicit codes work with it, but that doesn't help in terms of auditing the consents themselves, and when/how they were made.
Shocked this is not already in place.
We need to be able to export consents using the export module but this seems impossible currently as the Export module allows only Solicit Codes to be exported.
How quickly can this be enabled?
Is there a plan to add a feature that allows the export of all constituent contact consents? This is a critical requirement to ensure GDPR compliance and mailing/email status are always accurate ahead of supporter communications. Strange that it wasn't included as an option from the introduction of the consent tab.
The Consent Button is an improvement on the previous Attribute method for storing/tracing Consents, but you definitely need to be able to Export the Consents. Furthermore you need to be able to Global Add/Delete/Change/Replace on Consents too, seems odd you can do it on a manual basis but not globally - not great for database housekeeping.