Flow error when fetching Records in NPSP Org - Deprecated Fields

[jfeth-hillel]

Please excuse any omissions in submitting this issue as this is the first time I have submitted in Github.

Issue: Any Flow that references an Account record in an Org that has been updated to Winter 24' release and has the Contacts & Organizations Managed package (v3.22) installed as part of NPSP errors.

Error Example: Error Occurred: This error occurred when the flow tried to look up records: npe01__LifetimeDonationHistory_Number__c ^ ERROR at Row:1:Column:2859 No such column 'npe01__LifetimeDonationHistory_Number__c' on entity 'Account'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.. You can look up ExceptionCode values in the SOAP API Developer Guide.

---

---

Salesforce Error ID: 162201669-2081647 (254410713)

Explanation: Any Flow looking up and storing all fields on a Contact or Account record errors because the record contains fields deprecated by the Salesforce Managed Package that is part of NPSP.

Response from Salesforce: Hi Jerry, I checked with the team, and they say that because there are significant technical risks associated with the fix, it will be updated after winter 24. So, you can work accordingly with the release update. KI link:(https://issues.salesforce.com/issue/a028c00000xFymV/flows-fails-to-access-a-deprecated-field-from-managed-package )
Regards, xxxxx (name removed)

Remediation Request: It is my understanding that the owner of a managed package can update the package allowing any deprecated fields to be deleted by an admin of the org in which it is deployed. The current version of the Contacts & Organizations Managed package (v3.22) does not provide for this option.

The workaround described in the Known Issues article requires hours of work on our part to modify long existing flows to specifically identify the fields stored from the Account Record and avoid all of the depreciated fields.

I am requesting either an update mitigating this issue entirely or allowing the removal of the Deprecated fields in the NPSP managed packages.

[jamesbsfdc]

Hi @jfeth-hillel That field was deprecated from the package a long time ago. If you are not using the field you should be able to delete the field. Can you try switching to Classic and try deleting the field from there?