Archiving constituent attributes when changed by ImportOmatic
A
Amy Langer
started a topic
2 months ago
This is a bit of a pie-in-the-sky (and specific) dream, but I'm going to put it out there nonetheless:
We use Omatic Cloud to update values in an already-existing Constituent Attribute category. Currently, we can use Omatic Cloud to update the Constituent Attribute if the import has a different value than the existing value in the record.
However, we want a way to archive the previous value when it is replaced (like how in ImportOmatic, old addresses can be switched to a different category when a new address is found).
We've been able to build out a workaround by adding additional attributes for tracking and running through global changes/imports in RE Database, but having it be automated would save an incredible amount of time.
Amy Langer
This is a bit of a pie-in-the-sky (and specific) dream, but I'm going to put it out there nonetheless:
We use Omatic Cloud to update values in an already-existing Constituent Attribute category. Currently, we can use Omatic Cloud to update the Constituent Attribute if the import has a different value than the existing value in the record.
However, we want a way to archive the previous value when it is replaced (like how in ImportOmatic, old addresses can be switched to a different category when a new address is found).
We've been able to build out a workaround by adding additional attributes for tracking and running through global changes/imports in RE Database, but having it be automated would save an incredible amount of time.