| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T408451 Epic: Improve batch entry for DAF donation soft credits and shared addresses | |||
| Open | None | T408448 Create report to show soft credits and shared addresses for batch import | |||
| Open | None | T408449 On batch import, auto add soft credit & auto share addresses | |||
| Open | None | T408450 Backfill shared addresses for DAF's & related contacts | |||
| Open | None | T408259 Batch Data Entry update - Allow two soft credits in one field |
Event Timeline
After discussion with MGFE & donation processing, and some investigation of technical feasibility, we've decided a better long-term approach will be to avoid adding contact info to DAF contacts where the info would be shared with the DAF owner contact. In our ideal world, DAFs are just bare contacts that hold the contributions, while the email, address and phone live on the DAF owner contact. Donor segment, status and other calculated fields should include DAF donation soft credits.
In the case where the DAF has no owner and there are no soft credits, we will continue to treat the DAF as the contact we will email.
Steps to make this work:
- Include soft credits in contribution trigger calculations (including changes to the contribution table and the soft credit table).
- Backfill this data to some reasonable degree (perhaps our start of the fiscal year updates will be enough, TBD)
- Fix SearchKits used for exports of Thank you lists x2 to include soft credits
- Fix TY email to fetch email from DAF owner or soft-credited contact if no email present on DAF contact
- Adjust Acoustic export
- Fix MG SK for sending $5k+ TY letters
Subtasks of this epic will need to be reviewed and updating before starting work on this, though some tasks could be worked on independently (allowing two soft credits from one field in batch entry, auto add soft credit on batch import).