Optional email address in flow - Adobe Sign + Sharepoint

[MD7648]

Attempting to create an Adobe Sign flow and add optional email addresses to the flow, the flow fails when those fields are blank.  Otherwise the flow works fine with just one email address.

Ideally I want to send potential agreements to multiple people, it would also be nice to work out a way to change if those people are certified recipients or additional signee's. 

Here is the flow and errors: 

1) Document is uploaded to library and then flow manually started - navigate to emails

2) The flow itself is here with the options highlighted. 

3) these fields ask for Email1 or Email2 but the flow then fails if those fields are not entered by the user. 

The error is - 

'Create_an_agreement_from_an_uploaded_document_and_send_for_signature' inputs at line '1' and column '2088': 'The template language expression 'triggerBody()['email_2']' cannot be evaluated because property 'email_2' doesn't exist, available properties are 'entity, email'. Please see https://aka.ms/logicexpressions for usage details.'. 

I have looked at Set Variable option but don't see an option to insert Email1 or Email2 as variables. 

[abm · Accepted solution]

Hi @MD7648 

Try triggerBody()?['email_2']

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up.

Thanks

[MD7648]

Yeah that seems to sort it, cheers. I'm very unfamiliar with scripting and flows so probably a bit out of my depth.

Any way to customise the approver role or signing order? Theres no real user input for those. 

From what I can tell some of the Adobe Sign flow actions don't bring through variables or custom variables well.

[Anonymous]

Hi. You had the same issue I’m trying to solve. Would you mind sharing how you applied the solution which was suggested please ? Thank you. 

[Anonymous]

Hi. I have the same issue as you helped out with here . Would you mind sharing how it’s possible to apply your solution to the flow please ? Thank you. 

[abm]

Hi @Anonymous 

Place the cursor on the right field. Right hand side you have Dynamic Content and Expression. Click the expression and type

 triggerBody()?['email_2']

Makes sure you are using the right schema names email_2 or the related field name. Click ok.

Thanks

[Anonymous]

Thanks for replying so quickly - much appreciated 

[Anonymous]

Hi. Thanks - your reply solved my problem. It has raised a new one though which I wonder if I might also ask you about? I have a mix of internal and external email options (internal ones are just text). When I input only 1 internal, or 1 external, everything is fine, but if I have a mix of internal/external, or more than one of either type, the flow fails. It seems to be concatenating multiple email addresses together which create an invalid address overall.

I wonder if I need to somehow introduce a separator character in the expression somehow?

This is the only thread I've found (after a lot of searching) which seems to be getting me closer to a fix so any further help would be very much appreciated. Thank you in advance for any advice. 

[abm]

Hi @Anonymous 

Could you please create a new thread and post a screenshot of your run history and error details?

Thanks

[Anonymous]

Will do. Thanks