Previous Behaviour: When we attempted to sync transactions and create gifts in DonorPerfect (DP), sometimes the request would fail on the DP side. When this happened, Givecloud couldn't tell at which stage the request failed. The gift could have been created or it could not have. If the gift was created, we had no way of knowing the relationship between the gift in DP and the gift in GC. This meant that, upon failure, when we attempted the sync again, a duplicate gift would be created.

Updated Behaviour: When we push our transaction info to DonorPerfect to create a new gift, we now pass a new piece of information that will help us reconcile the gift in case of an error. When sending the request to create a gift in DonorPerfect, we now pass a reference into the GIFT_NARRATIVE field in DonorPerfect. Before sending the request, we look up gifts in DonorPerfect that have a reference to the item we’re trying to create. If one exists, we will link the item to that gift rather than create a duplicate. After a sync failure/disruption, the sync is only retried once, 5minutes later.

Previously when the "Show Gender" setting (Features > Site Design > Sponsorship) was un-toggled, it removed the gender language from the sponsee's profile, but not from the sponsor pop-up modal. We have update this setting to include both areas. When creating a sponsee profile, we also now allow you to select if the gender is unspecified.

Fore more info, check out the following article - https://help.givecloud.com/en/articles/1541656-getting-started-with-child-sponsorship#4-customize-website-sponsor-login-and-emails

This setting can be found on the Virtual Event set up page (Features > Virtual Events > Add).

Updates included: Ensuring that custom fields are sent on the line items in the response from the API and the data in a webhook.

Allowing users to filter the contributions index api endpoint by the following filters:

• ordered_before
• ordered_after
• updated_before
• updated_after

Updated documentation can be found here - https://developers.givecloud.com/api/contributions/

Check out more on how to use these tracking fields here https://help.givecloud.com/en/articles/3279013-supporter-acquisition-tracking

Previous Behaviour: When we attempted to sync contributions and create gifts in DonorPerfect (DP), sometimes the request would fail on the DP side. When this happened, Givecloud couldn't tell at which stage the request failed. The gift could have been created or it could not have. If the gift was created, we had no way of knowing the relationship between the gift in DP and the gift in GC. This meant that, upon failure, when we attempted the sync again, a duplicate gift would be created.

Updated Behaviour: When we push our contribution info to DonorPerfect to create a new gift, we now pass a new piece of information that will help us reconcile the gift in case of an error. When sending the request to create a gift in DonorPerfect, we now pass a reference into the GIFT_NARRATIVE field in DonorPerfect. Before sending the request, we look up gifts in DonorPerfect that have a reference to the item we’re trying to create. If one exists, we will link the item to that gift rather than create a duplicate. After a sync failure/disruption, the sync is only retried once, 5minutes later. Currently, this only applies to contributions and not to recurring transactions.