cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Zango
Advocate II
Advocate II

Send an email v2

Are there any benefits to use Send an email v2?

 

I thought it was that you could switch to a code view but I've realised editing a flow made with this kills my anchor even when I am not editing the link.

 

The regular Send an email has an option to make it html which doesn't get edited on save and actually works.

 

Will Send an email be replaced with the v2 version at some point? I cant see anything that it does better or even as well as the original.

 

Creating email with v2:

v2creating.PNG

Now after saving the email is messed up!

v2edit reg.PNG

v2editSaved.PNG

And results in killing the anchor in the email:

emailruins link.png

 

But with V1 i can just check the HTML box and it is created and edited correctly

v1.PNGj

and email that is sent:

emailv1.PNG

 

1 ACCEPTED SOLUTION

Accepted Solutions

Ok, this seems to have been my problem.

 

If the flow allows you to close the code view (if the button is visible and not grey) the anchor tags will get ruined as soon as the flow minimises the action. So if you save with the action open it will work but next time you come into the flow the action will have been minimised and replaced the working anchor so when you save again it saves the new ruined html.

 

Is there a set of rules when the code button becomes grey? I do think the HTML checkbox for Send an email V1 was a lot easier to understand.

 

If I wrap each part of the email in <p> tags or the entire thing in a <p> tag (code view is initialised wrapped in <p> tag) the button stays available so the link gets broken

wrapInP.PNG

but if i wrap the entire email in a div the code button stays grey and the email works
wrapInDiv.PNG

 

View solution in original post

11 REPLIES 11
Brad_Groux
Community Champion
Community Champion

You can use either Send an email or Send an email (V2) as you'd like. However, they are adding all new improvements to V2 going forward - and eventually, Send an email will likely be deprecated.

As far as your issues are concerned, it is important to remember that Send an email (V2) is currently available in Preview, which means it is still in active development - think of it as being in beta.

Because of this, it won't be perfect for the time being, there will be some minor issues using it. You are also encouraged to provide feedback when using preview items (which you are doing here =). 

SendEmailV2Preview.pngWith that said, as Send an email may eventually be deprecated, I'd strongly recommend that you utilize the Send an email (V2) if and when possible. That way, if the original Send an email is deprecated, you don't need to update your existing Flows to utilize the Send an email (V2)

NOTE: I do not have any information indicating that Send an email will ever be deprecated, however, going on their past improvements to existing connectors, actions and triggers while deprecating older ones - it is certainly within the realm of possibility that it will deprecated at some point in the future. But, it also may never be deprecated. 

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!

v-yamao-msft
Community Support
Community Support

Hi @Zango ,

 

I have made some tests on my side using action Send an email (V2) and Send an email, link to the item could be clickable for both of them.

1.PNG2.PNG

 

Could you take another try with it on your side?

 

Best regards,

Mabel

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi @v-yamao-msft ,

 

The first run through works and I get the email fine, its when when i go back in and edit the flow to add another action to the flow or another line to the Send an email v2 it seems to break the link.

 

I went through again and created the v2 email.

v2NewItem.PNG

Which is fine if then i add an item to the list i get my email through working.

v2firstrecieve.PNG

 

However now I decide i want to add some lines to the email (or add another action to the flow).

When i go to edit the flow the anchor part looks really messed up

v2edit.PNG

The anchor tag has been mutilated! 

If i decide to just go withit and add my line to the email and leave the rest as it is (maybe its supposed to do this encoding :3)

The email i get through is

v2blehlink died.PNG

The link is targeted at <object custom=

Hi @Zango ,

 

When you initialize the action Send an email (V2), please click the code icon to convert the view to Code view.

Then input the code you want in the Body field.

 

Per my certain test, once the view is converted to Code view and code are inputted into the Body field  at the beginning of setting up the flow, the code icon will be greyed out and not be clickable anymore.

 

Thus, the anchor won’t be changed. The link to the item will be working all the time.

1.PNG

 

Please tale a try with it.

 

Best regards,

Mabel

 

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
gamoraes
Memorable Member
Memorable Member

Hi @Zango ,  did you found the solution?

 

If yes, can you mark the solutions as accepted to help others in community?

 

Best Regards


Did I answer your question? Mark my post as a solution!

Gustavo Moraes, o astronauta brasileiro do Flow!


Ok, this seems to have been my problem.

 

If the flow allows you to close the code view (if the button is visible and not grey) the anchor tags will get ruined as soon as the flow minimises the action. So if you save with the action open it will work but next time you come into the flow the action will have been minimised and replaced the working anchor so when you save again it saves the new ruined html.

 

Is there a set of rules when the code button becomes grey? I do think the HTML checkbox for Send an email V1 was a lot easier to understand.

 

If I wrap each part of the email in <p> tags or the entire thing in a <p> tag (code view is initialised wrapped in <p> tag) the button stays available so the link gets broken

wrapInP.PNG

but if i wrap the entire email in a div the code button stays grey and the email works
wrapInDiv.PNG

 

Hi @Zango ,

 

Thanks for updating.

I will help collect and report this issue about action Send an email (V2) from my side.

Hope the workaround works for you.

 

Best regards,

Mabel

 

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi @v-yamao-msft 

 

i tried using Send an email v2 . Flow fails with and error message "Object reference not set to an instance of an object."

 

AHs anyone faced this kind of exception

Flow.PNG

 

Thanks,
Sru

viveka
Frequent Visitor

I had the same issue and your method (wrap the entire email in a div code) worked for me as well. 😃

If the flow allows you to close the code view (if the button is visible and not grey) the anchor tags will get ruined as soon as the flow minimises the action. So if you save with the action open it will work but next time you come into the flow the action will have been minimised and replaced the working anchor so when you save again it saves the new ruined html.

 

I know this is a super late comment but seriously, who would EVER know that if you close the html code preview for your email in Flow, it will not send as an HTML email...

 

Microsoft has GOT to be kidding to have removed the specific check to "render in HTML" and make some assumption that people would know to save their flow with the code template visible?   THANK YOU! I spent probably an hour trying to figure this out......

Thank you @Zango  - this has been causing me so much re-work today and it was making me crazy. 

Helpful resources

Announcements
MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

Power automate tips 768x460 v2.png

Restore a Deleted Flow

Did you know that you could restore a deleted flow? Check out this helpful article.

Microsoft Build 768x460.png

Microsoft Build is May 24-26. Have you registered yet?

Come together to explore latest innovations in code and application development—and gain insights from experts from around the world.

May UG Leader Call Carousel 768x460.png

What difference can a User Group make for you?

At the monthly call, connect with other leaders and find out how community makes your experience even better.

Users online (2,607)