With the Donor portal opened on FRUP, Donors would be able to update their emails at any time. However FRUP does not send any notification to CiviCRM on Contact update, we only know about this change on the next donation import.
We need to update the contact on CiviCRM when the donor contact details changes, using the donor external identifier.
This task specifically refers to times where we see a change come across on the audit file with a new donation.
@Damilare, can you confirm if "we only know about this change on the next donation import" refers to the nightly import, or would it be next time the supporter donates and that subsequent gift is imported?
@AKanji-WMF the latter is the case, we only know about after the supporter donates and the contribution is imported in the nightly imports.
@Damilare and @AKanji-WMF does this task also cover the case when DR updates a record of a donor who gave through FRU on Civi? This can happen when a donor contacts DR directly, and the team will only update manually on Civi.
As we don't have a two-way sync, how is that update going to show on FRU? Should we check the FRU team again on the API/Webhook or are there alternative solutions being considered?
Change #1014088 had a related patch set uploaded (by Damilare Adedoyin; author: Damilare Adedoyin):
[wikimedia/fundraising/SmashPig@master] Fundraiseup audit import for recur plan change
Change #1015383 had a related patch set uploaded (by Damilare Adedoyin; author: Damilare Adedoyin):
[wikimedia/fundraising/crm@master] WIP: Fundraiseup audit import for recur plan change
Change #1014088 merged by jenkins-bot:
[wikimedia/fundraising/SmashPig@master] Fundraiseup audit import for recur plan change
Change #1020416 had a related patch set uploaded (by Eileen; author: Eileen):
[wikimedia/fundraising/crm@master] Minor follow ups on Previous Fundraise up patch
@Damilare after thinking about our discussion today I decided to merge your patch as is & let you do further fixes as a follow up - this is mostly based on your comments that the code is not actually doing audit processing as yet - given that I think it's OK to merge in advance of the fix to ensure the code is in the right queue - which should reduce issues around code change / conflict affecting this patch
Change #1015383 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Fundraiseup audit import for recur plan change
Change #1020416 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Minor follow ups on Previous Fundraise up patch
Change #1021470 had a related patch set uploaded (by Damilare Adedoyin; author: Damilare Adedoyin):
[wikimedia/fundraising/crm@master] Fundraiseup audit import for recur plan change, push msg to the recurring-upgrade
Change #1021476 had a related patch set uploaded (by Damilare Adedoyin; author: Damilare Adedoyin):
[wikimedia/fundraising/SmashPig@master] Push Fundraiseup modify msg to recur-upgrade queue
Change #1021476 merged by jenkins-bot:
[wikimedia/fundraising/SmashPig@master] Rename Recurring upgrade queue to Recurring-modify.
Change #1021470 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Fundraiseup audit import for recur plan change, push msg to the recurring-upgrade