#Receipt0 debatiendo

I was asked by some admins to come up with a demonstration of setting a contact lookup field on opportunity to that of the the primary donor contact role. Here is my solution. What issues do you see? And do you have ways to solve some of the shortcomings?

1) Setup PB to run each time an opportunity it created or edited. Calls flow passing in opportunity ID.

2) Flow gets primary contact role and copies corresponding contact ID to a custom picklist field Primary_Contact.

This seems to work fine upon the following situations:

o creating a new donation using the UI

o editing the donation using the UI

o updating the donation through Apsona (but batch size must be less than 100)

o importing donations through Apsons (but batch size must be less than 100)

I have proven that this runs only once during NPSP 3.0 for the above situations.

It fails to update if you change the primary donor contact role from one to another role, if you add a brand new primary control role, or if you delete the primary contact role. Apparently these are not changes to the opportunity.

Finally, there are limits apparently to how many times a flow can do things to the database when invokes in batches. So you have to keep batch size under 100 to avoid failures one would normally see if you have a flow the looped and queried the database too many times.

Many admins want this type of contact lookup field for receipting. I guess it's available in one or two of the not-NPSP platforms build on Sf. I'm even considering it myself so that I can accomplish receipt generation fully native.

, I have a (probably) quick question I'm hoping you can help with. I'm just getting started with it.

I want to use it to send receipts to donors. We send all receipts by postal mail.

The context:

* Opportunities are used to track donations

* Checkbox indicates whether or not the donor has been thanked

* All individuals and all organizations get their own account; there are no contacts under accounts. To track employment relationships, we exclusively use affiliations. Therefore, the Opportunity.AccountName will always be the actual donor -- either an individual's name (their 1:1 account), or the organization's name. We have a required opp pick list that specifies whether it's an individual or a business/entity donation.

* For donations from organizations, we use the Contact Role to indicate who the primary individual at the organization was. Contact Role of "Donor", and checked for Primary.

I've uploaded a Word doc template file as our receipt. The address block references

and Account billing address.

I would like the "Dear __________" line to be their first name rather than Dear

, because that could be either Dear First Last (impersonal), or Dear Acme, Inc. (even more impersonal when we know who the primary person was at the organization).

I also need the address block to have the name of the Primary contact role individual if there one.

So how do I do these 2 things? In Apsona, I do the following to get started:

1. Click into Apsona's "Opportunities" tab

2. Filter to see only the donations that still need to be thanks/receipted

3. Click Tools / Mail Merge

4. Create a new action

5. Specify a single .DOCX file

6. Begin mapping fields

And that's where I'm lost. All the merge fields have a mapped value, except for Apsona.FirstName (the name of the field in the Word template). When I look at the long, long list of all the data fields it has for me to pick from, I can't find anything for Contacts -- so there's no first name, no last name option; just account name. Nor am I able to find anything that would seem specific to the contact role marked Primary.

Any help much appreciated.

dt