Skip to main content
Nintex Community Menu Bar
Solved

Email multiple external recipients

  • December 12, 2016
  • 8 replies
  • 26 views
  • Translate

Chris_Ben
Nintex Employee
Forum|alt.badge.img+14

Hi team,

 

Does anyone know how to send an external email from o365 to multiple external recipients?  I'm not sure what data type to use.  I've tried a semi colon delimited text variable, dictionary and collection variables.  All throw an exception with the error:

 

RequestorId: f461f2f8-3567-47ef-0000-000000000000. Details: System.Activities.Statements.WorkflowTerminatedException: SharePoint operation 'GetUsersByGroupNameAsync' did not return successfully. Status Code: [InternalServerError]{"odata.error":{"code":"-2146232832, Microsoft.SharePoint.SPException","message":{"lang":"en-US","value":"Group cannot be found."}}}

 

Cheers,

Chris

Best answer by TomaszPoszytek

Chris Ben‌ of course you can do it. However to achieve that be aware of two things: first, that you declare the list of recipients as a text variable, emails delimited with semicolon (onuser@mail1.com;user2@mail2.com;user3@mail3.com), that you then put in the action's "To:" field. Second one, which I faced and almost made me crazy - "External email" does not trim the values. So be sure there are no spaces in the string. Mails have to be delimited but without a single space .

Regards, Tomasz

View original
Did this topic help you find an answer to your question?

8 replies

Forum|alt.badge.img+16
  • 914 replies
  • December 13, 2016

The help information (Send an Email ) does not mention that you can set multiple values, so it's sure that it is not currently available.

In that case you could make a loop and send an email inside your loop

Translate

Chris_Ben
Nintex Employee
Forum|alt.badge.img+14
  • Author
  • Nintex Employee
  • 360 replies
  • December 13, 2016

Yes, I suspect so too Fernando.  Actually the documentation doesn't say either way so I guess we have to assume it only accepts a single recipient.  Anyone else know for sure?

Cheers,

Chris

Translate

TomaszPoszytek
Forum|alt.badge.img+17

Chris Ben‌ of course you can do it. However to achieve that be aware of two things: first, that you declare the list of recipients as a text variable, emails delimited with semicolon (onuser@mail1.com;user2@mail2.com;user3@mail3.com), that you then put in the action's "To:" field. Second one, which I faced and almost made me crazy - "External email" does not trim the values. So be sure there are no spaces in the string. Mails have to be delimited but without a single space .

Regards, Tomasz

Translate

Chris_Ben
Nintex Employee
Forum|alt.badge.img+14
  • Author
  • Nintex Employee
  • 360 replies
  • December 14, 2016

Tomasz, you are a legend.  My variable was delimited with a semicolon and a space.  After a quick RegEx to remove the spaces, I'm up and running.  Thanks!

Translate

TomaszPoszytek
Forum|alt.badge.img+17

I'm glad that I helped you. I even raised a ticket at Nintex after many hours of trying to solve it on my own, then I received their workflow where they proved it is working fine and then after comparing the strings I noticed the spaces. After removal it works ok.

I asked Nintex to make a correction to the O365 backend code, so that it is not vulnerable and trims the strings, but it was just a month ago.

Funny thing is that when using "internal email" option spaces do no harm

Translate

Forum|alt.badge.img+17
  • 1129 replies
  • December 16, 2016

I'm so glad you found that and also posted here how to solve this. Great job ‌!

Translate

juandyer

I'm having this very same issue at the moment and trying to apply the solution suggested by Tomasz. Can someone point me to details as to how can I "declare the list of recipients as a text variable"?

Translate

  • 4 replies
  • September 5, 2019

And three years later it is still not fixed by Nintex. Thanks for your help.

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings