Add-In Button Acknowledgement Letter Flow That Pulls Addressee and Salutation

Joseph Stiger

Does anyone have a template or would know how to go about setting up a flow that pulls the addressee and salutation instead of first, middle, and last name? The default template only pulls the latter. Any help would be appreciated. Thank you.

Austen Brown

@Joseph Stiger - You'll need to add a few additional steps to the flow, namely “get constituent name formats” within the Constituent connector. From there you can update your templates to accept add/sal instead of the donor's name.

Alex Wong

@Joseph Stiger
This is the connector and action to use:

and provides it with the constituent system id:

Joseph Stiger

Letter

@Alex Wong Would you happen to know what additional action(s) I would need to add? As of now, this is what is generated. I appreciate the help.

Alex Wong

@Joseph Stiger
use the Dynamic content of Primary addressee formattted name or Primary salutation formatted name from the Get constituent name format summary action

Depending on your usage, if there is potential for the constituent record you are working is a org record, then you will need to condition on the salutation being empty and use something else instead. For example, if you want to say Dear "Friend", when it's an org record, then you need to use an Expression:

if(empty(outputs('Get_constituent_name_format_summary')?['body/primary_salutation/formatted_name']), 'Friend', outputs('Get_constituent_name_format_summary')?['body/primary_salutation/formatted_name'])

same can be applied for the addresee, where if org record, output the name of constituent (which is org name) in an Expression:

if(empty(outputs('Get_constituent_name_format_summary')?['body/primary_addressee/formatted_name']), outputs('Get_a_constituent')?['body/name'], outputs('Get_constituent_name_format_summary')?['body/primary_addressee/formatted_name'])

Sandra Ross

@Alex Wong Hi Alex, I have our acknowledgement flow created using “primary” addressee and salutation using the previous RE Constituent connector. Do I have to rebuild the flow using the new connector that includes the additional addressee/sals or can I add it in on my existing flow as I did for the “primary” rather than name? I also have the issue of needing an if/then expression (if that is possible) as we use Addressee 2 and if that is null, use Addressee 1. Below is a screenshot of where I am in the flow and ready to create the expression to use the particular addressee type. Any guidance or suggestions appreciated!

Alex Wong

@Sandra Ross
what you are using to get addressee/salutation is already the current connector not previous.

Previous BB connector (checkmark under)

Current BB Connector for Constituent

So the one you use will get you the additional addressee/salutation.

I do not know what you mean by “addressee 1” vs “addressee 2”. There is the primary addressee, which there is only ONE per constituent, and then there is the “addtional addressee/salutation” that a constituent can have many.

The Get constituent name format summary will return one object of primary_addressee, one object of primary_salutation, and an array of object additional_name_formats.

"body": {

"additional_name_formats": [

{

"id": "1",

"configuration_id": "1",

"constituent_id": "415427",

"custom_format": true,

"formatted_name": "ABCDE",

"type": "Publication Name"

}

],

"primary_addressee": {

"id": "778BD6D0-AA44-4C45-B9DC-E872E934A103_415427",

"configuration_id": "51",

"constituent_id": "415427",

"custom_format": false,

"formatted_name": "ABC",

"primary_type": "Addressee"

},

"primary_salutation": {

"id": "D17C0B9C-BADE-4A9E-8CE6-85ADA93C21EE_415427",

"configuration_id": "53",

"constituent_id": "415427",

"custom_format": false,

"formatted_name": "ABC",

"primary_type": "Salutation"

}

}

you can experiment with:

empty() to check if a dynamic content exists or not
Filter Array action to filter and get a specific “type” of addressee/salutation in the additional_name_formats array.