Select to view content in your preferred language

Adding Survey123 signature to Power Automate flow

4411
32
Jump to solution
03-04-2024 07:29 AM
AshleyPeters
Frequent Contributor

I have a flow set up in Power Automate following Ismael's Survey123 Tricks of the Trade blog post. I'm trying to modify it a bit so I can include photos from one question and a signature as email attachments in Power Automate. I've basically created two arrays, one for the photos and another for the signature. I've tried feeding those directly into an email, but I get an error with trying to attach the two arrays. I either need to find a way to combine the two arrays into one before I pull them into an email or find a way to embed the signature into the email. If I pull the signature into the email itself, Power Automate sends a separate email with the signature attached.

Has anyone else tried this? I'm fairly new to Power Automate, so my understanding of it is limited.

Thanks for any guidance!

Ashley

0 Kudos
32 Replies
abureaux
MVP Frequent Contributor

Even though your "Create report" steps shows success, that is where the error is. Esri's connectors tend to do this a lot, where the "fail gracefully" in that they do fail, but since they successfully identified the fail, it counts as a success.

We can tell this is the case because the HTTP step asked the Create Report step for some data, and it got nothing (i.e., null) back.

What you need to do is expand the Create report step, and there should be an error message buried in one of those fields (within Create Report, I believe it is the very last or second to last box that has what you want)

AshleyPeters
Frequent Contributor

Found the error: 

"binde type esriAttachment for question Signature is not constist with feature layer field type esriFieldTypeString"
 
And the survey and flow haven't changed since this was set up and running properly, but at least I now know.
 
Thank you so much for showing me where to look!
AshleyPeters
Frequent Contributor

Thanks again @abureaux for your help! I had to delete the signature field from the feature layer then it worked perfectly again.

0 Kudos