As I'm envisioning it though, keep in mind that you would be going through the full import process, then it could pop up a msgbox at the end and say "There were 8 exceptions, do you wish to commit this import?". If you choose "No", the import would not be committed and you would still have your exceptions file to make fixes, but you would need to do the entire import again a second time. Is that roughly what you'd like
We're adding a free, open API to Import-O-Matic!The question about info source is a good one, we'd probably need to dive deeper into the specifics to find out. It does give me an idea for adding a new programming event like "MatchFound" or something that will let us execute some code as soon as an existing constituent is matched to. This would allow us to check/cache certain field values and we could then verify them in the BeforeConstituentSaved event. Even more specific to the issue you mentioned might be an "AddressAdded" event, that would allow us manipulate the address (say, set the info source) only when it is a new address being added. Thanks for the ideas, I'll see if we can add some of these events.
Posted By James Hoare on 04 Apr 2012 03:33 AMHi James,
When we add new reccuring gifts to a record through I-o-M it would be great if the system could close off any existing recurring gifts on the constituent'srecord as part of the import process.