I have a new computer now and in my old computer i had a customized omatic plug in in my Raisers Edge
How can I get that back on to my new computer
Posted By Katie Moller on 20 Feb 2013 03:35 PM
I have a similar question on non-constituents. Because we import from Convio and our database and Convio don't always have the same information (hoping to fix that with the connector soon!), I don't know if someone is a constituent or a non-constituent before importing. I am relying on IOM to do a check, but I don't want to create constituents where I want a non-constituent in the Event Module. I tried using the Y/N for Participant is Constituent, but when used on someone who IS a constituent - marking them N because there was no ID number in the Convio export that I import from - it made an exception instead of just creating a non-constituent relationship. What I want it to do is to create a non-constituent participant when a matching constituent isn't found in the database. Is this possible?
Right now, IOM will create an exception if you import a participant with 'Participant Is a Constituent' = N and match it to an existing full constituent.
So you can run your import in two steps - the first time importing the non-constituents and the second time importing the constituents.
1 - Import all of your participants and use the mapping for 'Participant Is a Constituent' and set it to 'N' for everyone - this could be set in a virtual field rather than adding it to the file if you like. Anyone who is not matched to an existing constituent will be imported as a new non-constituent participant. Anyone who is matched to an existing constituent will create an exception and not import.
2 - Import again using the exceptions file instead of the original file. Remove the virtual field or set it to ignore the 'Participant Is a Constituent' field. Match these people to their constituent records - they will import as constituent participants.