Newbie to the API so please be nice! Looking at the potential of moving the Data Protection Preferences from Solicit Codes across to Constituent Attributes so dates and comments can be recorded (will also work nicely with Chimpegration).
Is it possible for an import profile to be setup to not create a duplicate constituent attribute in a case like this:
Constituent Attribute Category: Data Protection Preferences
Description: Email Opt-In OR No Mail OR No Phone OR SMS Opt-In
Let's say my RE record already has the Constituent Attribute Description of Email Opt-In and another of No Mail for this Category. The file I'm going to import contains the same Category with Description of another Email Opt-In. (Each Description option would have it's own specific column)
If we were to use the standard 'Update existing' function this could overwrite the Constituent Attribute with No Mail into Email Opt-In, thefore losing the preference. If the 'Add new attribute' function is used this would create duplicates of the same description.
Is it possible to code something in the API to recognise the Constituent Attribute Description and treat it differently for this?
Also if a value is blank in the import file's specific Description column, can the API be called to delete the matching Attribute (e.g. my record has No Phone, but the latest donation form I completed did not opt out of phone calls - so the import field of No Phone will be blank meaning I can be contacted by phone).