Mailto for multiple recipients in Outlook
Hi. When I set up a mailto with commas separating the recipients Outlook tells me I need to change the commas to semi colons. When I change the list of recipients in Anaplan to use semi colons as separators no recipients appear in the draft email. Has anyone else experienced this and found a solution. N.B. We have central settings in Outlook so I can't change the preferred separator to commas. Every other aspect of the email works correctly - e.g. subject text etc.
My current workaround is generating individual emails to each user, which isn't ideal.
Thanks
Best Answer
-
Hello, not sure if topic has been solved on another link , but i noticed i can use the ";" as separators in the "To" field, while running the mailto function from NuX page. If i run mailto function from backend module it puts blanks in the To of email , somehow does not recognize the "To" field. Not sure how possible , but please share here if others have the same .
1
Answers
-
There was a similar thread on this topic, and I believe the separator for Anaplan needs to be commas and not semicolons. See here for more info: https://community.anaplan.com/discussion/comment/149015/#Comment_149015
0 -
Thanks all for your responses. Semi-colons can't be used - only commas unfortunately. Our Outlook settings are not configurable under company policy. I think Ryan's link is most likely - something to do with my company's outlook settings. Thanks all.
0 -
By using the MailTo in your href links in HTML files, you can manage multiple recipients in a semicolons seperated format. You can also set a default subject field text for the email. Also it is possible to set the Copy To or the CC field values by typing the recipients for the CC field value.
-5 -
Hi @Sherrieward ,
Can you please provide some more details on how to achieve this?
Regards,
Aakash Sachdeva
0 -
I noticed this a few days ago too Andreea. I did get a new version of outlook at that time so thought it was just that but I hadn't noticed that it doesn't work in the backend. Just tried it and can confirm it only works on the page, which is good enough for now.
0