We have a couple custom fields for tracking how to recognize a donation gift using
#NPSP. One is a checkbox to indicate whether the donation should be anonymous. The second field is a text box for entering free-form how the donation should be recognized in public materials (annual reports, etc.)
Our receipts still are addressed to the Opportunity Account Name, but our mail merge templates want to show the donor recognition status.
Setting up a workflow so that:
1. If Donation_is_Anonymous checkbox is checked, set the Recognize_Donation__c text box to the value "Anonymous"
2. If Donation_is_Anonymous checkbox is NOT checked, set the Recognize_Donation__c text box value to the opportunity's account name ONLY if nothing has already been entered into the Recognize_Donation__c text box.
That way, if it's anonymous, it uses Anonymous as the value, and if I specified no explicit recognition, it assumes the
account.name(which is the donor's 1:1 account or the entity if it's an organization's gift) is the donor to be recognized...unless I've indicated something else in the field. (Say, a wife and husband, or The xxx Family).
Formula is failing with "Error: Formula result is data type (Boolean), incompatible with expected data type (Text)."
IF ( Donation_is_Anonymous__c == TRUE,
Recognize_Donation__c = "Anonymous",
IF ( Recognize_Donation__c = "",
Recognize_Donation__c =
Account.Name,
Recognize_Donation__c = Recognize_Donation__c
)
)
@Judi Sohn , that ALMOST does it! I opted not to include it in the workflow criteria since it is conceivable that a user may check the anonymous box AND enter something into the Donor Recognition field. Illogical, but far more illogical things have been done in the harried times folks spend trying to rush through piles of donations to enter.
So the first test has to be against the anonymous checkbox as a business rule priority over whatever is entered into the field.
It seemed easy enough to fix the workflow using your guidance, and
@Ashima Saigal's, that I don't need to reference the object being updated. I would've expected it to work either way, but knowing that clears it up.
Now, it works fine most of the time, but not consistently after the record is created. I'll keep playing with it.
Thanks all for the help.
dt
