Can't figure out why this is. I have created an email using Mail send notification V3. When I change the font color and save. It will send one email with that font color then it reverts back to black. If I save it then go back in it has reverted back to black. Any ideas what is going on here?
Wow @DamoBird365 I think this can be really good workaround for this kind of problem, I checked it and I think this can work. This might have been the one that looks similar to some way I might have been using before - this way might be even simpler actually.
Essentially, what you can do @StephenGW is following:
1) First two steps only of my previous reply.
2) Switch to HTML mode.
3) Copy the HTML code.
4) Switch it back to Rich Text mode.
5) Paste the output in a Compose block that is placed before the "Send an Email" kind of action.
6) Use the Outputs of Compose block directly in the Rich Text editor.
7) Email will contain the color intact, and the Rich Text editor can still be used.
You can check results of my test below:
A) The test Flow looks something like below:
Even if the Action I used is Send an Email (Outlook) rather than the one you used ( the one you use, I believe routes the e-mail through a 3rd party called SendGrid, whereas the one I use in my example does not do this ), here's what happens. Wwhen performing the steps of my original post on that action block, it still reverts back to strip the color out when changing it back to Rich text Mode from HTML mode, so as I suspected it is probably same issue which happens with all Flow Actions that use that similar kind of Rich Text Editor convenience control.
Anyway here is test result below:
Even if it is HTML from Compose block placed dynamically in Rich Text Editor, it works.
It also worked, on a second test as well.
One other detail I checked on:
@StephenGW wrote:
When I change the font color and save. It will send one email with that font color then it reverts back to black.
When I tested this, that does not seem to be exactly what's happening. As long as I did not change the contents of Rich Text Editor, the color would not be removed. The color did not even remove after I re-saved the Flow, not even if there were changes such as an additional whole step added to the Flow, for example (even after seeing that the Rich Text Editor contents did "revert to black" as you said it did). Instead, what happens to me is that only after I changed or added any contents of the Rich Text Editor itself and then re-saved the Flow, in that case it sent the new contents exactly with it "reverted to black" in the way you described.
When using the way suggested by @DamoBird365 this does not happen, the color stays intact, and when using @DamoBird365 's way it is possible to keep the Rich Text Editor on - this can be helpful for at least iteratively building snippets on the control, then arranging them together with a series of one or more Compose blocks, for example.
I tested and my method I originally posted works as well. The Compose can also be placed in the HTML view too. However, the downside is not using the Rich Text Editor anymore at all. With this way above with the Compose block, at least the Rich Text Editor control can still be used in some way.
Check if it helps @StephenGW
I have done what you suggested. It will probably be a while before this gets tested as we only use if a few times a week. I will leave it in the HTML mode and see if that fixes it. I will report back either way when I know.
Thanks
Hi both,
Just a thought, not sure if it will help, but can you insert the html for the red header in a compose and then use the compose dynamically in the email body? The editor cannot change the compose but will it read it as html or plain text? I’m not in front of a PC, so I cannot try.
Damien
I can see what you mean, check if below works as a test:
1) Try putting your color change and size change there again.
2) Click on this button: </> as shown below:
3) Now notice you see the HTML view below:
What the problem is now, is that if you click the button </> again right now, it will revert to black, and then if you click it again, it will show some of the code stripped out as well.
If you happen to do that, then repeat Steps 1, 2, and 3 above, and then do the following step instead:
4) Press return at the end of the line to insert a line break, or do any other kind of change of your choice that will grey out the </> button, as shown below. Some changes will not grey it out, so make sure it is greyed out.
5) Check if the issue persists.
I remember that I did encounter this kind of issue before. A long time ago I encountered it with the Outlook Office 365 Send Mail or any other Action that has this similar kind of control. This issue looks similar to that issue I encountered before - maybe it is still there for all those rich text kind of Action editors.
If the above way works, please indicate here, as I did not specifically test it right now for this case.
If the above way does work by the way, I am unfortunately not aware of any other way (i.e. such as a way that doesn't require forcing the HTML view) than just this way I have here.
Just beware if using this way. If relying on this way, then once making it to grey it out, do not switch it back just to edit it with the rich editor for convenience - it will strip the code again and revert it again, and the more code there is, the more code it might strip out. If this way I described here works, I am not aware of another way.
A long time ago, it is possible that with some very specific edits to the HTML, or some other bizarre steps I came up with before, I was able to get it so the editor would not revert back the changes - however, I do not recall the steps (or if they even exist, it is possible I just did it this way here) - or even if such steps existed if they work now anymore. For now please try the above and indicate if it worked at all.
If it works, but you still need solution which must use the rich text editor not to revert back the changes rather than using HTML only, please indicate as well - for now I also have same issue, can reproduce the issue as well, and can only think of above solution for now.
WarrenBelz
146,731
Most Valuable Professional
RandyHayes
76,287
Super User 2024 Season 1
Pstork1
66,077
Most Valuable Professional