Approval Markdown Incorrect Styling - Bug?

(0) Share

Report

Posted on by Codesidian

I have a flow that builds a string, containing markdown, and inserts it into the details field in an approval action:

and in the approval action:

The additional info string is populated like this:

The string that's being stored in a list item shows valid markdown:

The actual run history of the flow shows valid markdown:

However, this is the approval email:

The first comment should not be a header. It isn't stored anywhere with that syntax, and the run history doesn't show it with that syntax. There's also an issue with the horizontal rules, that although undocumented, do seem to render sometimes. So what is going on here and does anybody know how to fix this?

All responses (1)

Answers (1)

Verified answer

Codesidian 33 on at

Like (0)

Report
Re: Approval Markdown Incorrect Styling - Bug?

Managed to figure this out. The problem is with spacing. For some reason this happens when single line spacing is used such as:

# Header *italic text* normal text: hello world *italic text* normal text: Lorem ipsum dolor sit amet

Switching to double line spacing, which i believe some flavours of markdown require, renders the output as expected. Double line spacing would be like so:

# Header *italic text* normal text: hello world *italic text* normal text: Lorem ipsum dolor sit amet

Where a full break would be the next line and two breaks create a space between the paragraph lines. This seems to contradict the documentation on this topic outlined here. Anyway, hope that helps anybody who may stumble upon this.

Will just add the power automate examples:
^ how the additional information list field is populated.

^ the additional information var

^ Approval action

^ Final approval output email.