We get donation export files from our oniline Credit Card system which include all transactions, including those which have failed. (just for info, there are reports on just successful donations but they do not include the donors details, so changing the type of report we use to obtain the export files isnt an option)
is there a way in importOmatic to specify that only rows where (for example) Column G = "Success" should be imported and everything else should be ignored?
Id rather not have to get users to sort export files and delete unwanted rows, would be better if the import function took care of this for us
Is this possible?
thanks for the info -
we dont have a programmer so the API route may be trickier to do, but the mapping of constituent ID may be possible. however ive realised there is an added compllication:
In the reports we receive the following:
|PAYMENT||OK||0000 : The Authorisation was Successful.|
|REFUND||OK||0000 : The Authorisation was Successful.|
I only want to import rows where TxType = Payment and StatusDetail = 0000 : The Authorisation was Successful.
Currently, we are opening the file and sorting it, deleting rows etc, but it would be great if there was a way to automate this (and minimise the chance of errors)
Status will sometimes be a failure notification, for example: "5011 : Your card number has failed our validity checks and appears to be incorrect. Please check and re-enter."
Hi Jeff -
Interesting idea. I'm working on a similar import problem and would like to give this a shot. Question though: if you map the success/fail column into the constituent ID, and then use the dictionary to overwrite the field as blank, what would IoM have to match on in order to import the record? Wouldn't you just have a blank value instead of a constituent ID?
It's premised on the idea that the import file does not actually contain a column for the Constituent ID. If you have an invalid constit ID in your file IOM can kick that out as an exception. If the Constit ID column is blank, it will then use it's duplicate searching capabilities to find a match based on biographical data. Definitely check out the duplicate matching criteria if you haven't already, it's one of the best parts of IOM and just got a lot better in IOM 2.3.
Let us know how it goes!
Here's the link: http://omaticsoftware.com/Forums/tabid/108/aft/333/Default.aspx
To manually navigate to it:
* Under the gray bar for Raiser's Edge, look for the folder: ImportOmatic API
* The documentation is the first item in the forum. There is a red pin next to it.