W-10288878: Work Elevate - Ingest Tribute Information - Part 1/2

[grivero]

W-10288878: Work Elevate - Ingest Tribute Information - Part 1/2

• New custom metadata fields to support tribute info mapping

• New custom fields to support tribute info

• Updates on Install script to create tribute mappings

• Updates on Donation layout to include new tribute custom fields

• new Custom Metadata Types:

  • Data_Import_Field_Mapping.Donation_Honoree_Information.md-meta.xml
  • Data_Import_Field_Mapping.Donation_Honoree_Name.md-meta.xml
  • Data_Import_Field_Mapping.Donation_Notification_Message.md-meta.xml
  • Data_Import_Field_Mapping.Donation_Notification_Preference.md-meta.xml
  • Data_Import_Field_Mapping.Donation_Notification_Recipient_Email.md-meta.xml
  • Data_Import_Field_Mapping.Donation_Notification_Recipient_Info.md-meta.xml
  • Data_Import_Field_Mapping.Donation_Notification_Recipient_Name.md-meta.xml
  • Data_Import_Field_Mapping.Donation_Tribute_Type.md-meta.xml

Critical Changes

Changes

Import or Enter Tribute Gifts

• We added tribute gift fields to Gift Entry and NPSP Data Importer. The new fields on the NPSP Data Import object map to the Tribute fields on the Opportunity. These fields also work with tributes on Elevate Giving Pages.
• Update your users' permissions for the new fields:
  • NPSP Data Import object:
    • Donation_Honoree_Information__c
    • Donation_Honoree_Name__c
    • Donation_Notification_Message__c
    • Donation_Notification_Preference__c
    • Donation_Notification_Recipient_Email__c
    • Donation_Notification_Recipient_Info__c
    • Donation_Notification_Recipient_Name__c
    • Donation_Tribute_Type__c
  • Opportunity object:
    • Honoree_Information__c
    • Notification_Recipient_Email__c
    • Tribute_Notification_Date__c
    • Tribute_Notification_Status__c
• If you have existing NPSP Data Import fields and mappings for the Opportunity tribute fields, we recommend deleting your old fields and mappings and use the packaged ones instead.

Issues Closed

Community Ideas Delivered

Features Intended for Future Release

Features for Elevate Customers

New Metadata

• Fields:
  • DataImport__c.Donation_Honoree_Information__c
  • DataImport__c.Donation_Honoree_Name__c
  • DataImport__c.Donation_Notification_Message__c
  • DataImport__c.Donation_Notification_Preference__c
  • DataImport__c.Donation_Notification_Recipient_Email__c
  • DataImport__c.Donation_Notification_Recipient_Info__c
  • DataImport__c.Donation_Notification_Recipient_Name__c
  • DataImport__c.Donation_Tribute_Type__c
  • Opportunity.Honoree_Information__c
  • Opportunity.Notification_Recipient_Email__c
  • Opportunity.Tribute_Notification_Date__c
  • Opportunity.Tribute_Notification_Status__c

Deleted Metadata

[mldyang]

Looks good.
Currently, the Feature Test is failing. But, it doesn't seem to be related to this work. I re-started the build to see if that will resolve the issue.

[klewis-sfdc]

Looks good. Currently, the Feature Test is failing. But, it doesn't seem to be related to this work. I re-started the build to see if that will resolve the issue.

Looks like the rebuild passed. And I can confirm that the tests that failed on the first run are flaky and fail occasionally.

[klewis-sfdc]

This field type change should be fine when upgrading existing orgs, right? I think this is the equivalent of modifying the length of a text field as mentioned here: https://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/modifying_custom_fields.htm. @grivero Is that your understanding also?

[grivero]

@kenlewis-sfdo, this type of conversion is allowed and it's safe to update field type.
This article also have good notes about field conversion: https://help.salesforce.com/s/articleView?id=sf.notes_on_changing_custom_field_types.htm&type=5

[klewis-sfdc]

Sounds good! Thanks, @grivero

[callen-sfdo]

Reviewed and tested, looks good.