We need an advanced address processing screen in the Omatic Cloud. Right now my choices are to import addresses without knowing if they are valid, or ignore addresses.
We also need to be able to update a new address while saving the old address as a former address.
Hi Sarah - Thank you for putting the idea on our forums. I hope things are well with you all up in BC!
Thank you for the great detail of why you would need this info and also challenges you are facing. Any other information and opinions you have about situations you might encounter with addresses would be helpful. Do have similar issues with other types of records apart from addresses (e.g. emails, phones, attributes/custom fields)?
We know we need to look at how we can enable more robust business logic on our "child" objects that drive decisions and behaviors when adding/updating that data in your applications. This is not unique to RE but could be applied to other applications such as Salesforce as well. Addresses tend to be a big one as we know all of our clients need to have accurate address data as well as archiving previous addresses.
Hi Steve, So far I haven't noticed an issue with phone or email types, but we do allow multiple of the same type (e.g. we can have 3 numbers with the same type). I like this because it means we can mass update inactive numbers through importing after a calling campaign.
I do however wish Comments for the phones was available in web view, but that's a Blackbaud problem. We use the Phone Comments to input where the number came from (e.g. Source: Luminate Online).
I'm with Sarah on the Advanced Address processing especially related to copying to Previous. This is one of the big advantages of ImportOmatic that didn't come along with Omatic Cloud and I'm noticing it's absence.