Stewardship Contact Uploads:

Currently the way the system works for a donor contact with one fund:

If it does not match on the primary fund file field (eg. Fund Code in Fund File) then the system uses the fallback code on the portfolio to do the matching (eg. Fund Code in the Portfolio).

But if a donor contact has more than one fund and does not match on the primary fund file field (eg. Fund Code in Fund File) the system it works this way: For each row in the file, the way the fallback works is if it finds a fund in one of the steps, it stops falling back. So if it finds three funds by using the fund file field it stops looking so if the 4th fund doesn't have that field it does not look at the fallback and that fund doesn't get matched.

This means that a donor contact with multiple funds may have all of the fund fields for that last fund listed out but it is not actually matched to that fund.

Would it be possible to update this functionality so they system would continue looking for that fallback code, at least until it has as many Funds matched as it does Fund Codes?

Adding fund codes (or other fields) as multi-select fields in the file ensures that all fund codes (or other fields) are listed in that Donor Contact record. If the file was loaded with the same donor on each row the donor contact record would only include one fund code.

For more info please see Jira BBAM-3468

Fallback not wo...

Attachments Open full size