You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a Logic App, using the Sentinel logic-app connector (Add comment to incident (V3)) in a For Each loop and entering a simple HTML table as the comment causes the table to be prefixed by many <br> tags upon presentation inside the browser leading to an unprofessional looking comment.
To Reproduce
Steps to reproduce the behavior:
Make a simple logic app that iterates over some sample data in an array via For Each
Use the "Add comment to incident (V3)" connector function to post a comment to a sample incident inside the For Each
In the comment, add a title describing the table, ie, "This is my test data"
Press enter 3 times
Make a simple HTML table with 10 or so rows in the table from sample data
Execute the logic-app and look at the comments in the Sentinel incident
Expected behavior
A comment with a title, a newline, then the table presented graphically (without excessive newlines between title and table)
Desktop (please complete the following information):
OS: Windows 10
Browser Chrome
Version Latest
Additional context
Using Chromes "inspect" feature to inspect the HTML in the relevant comment, expanding the relevant <div>, Sentinel seems to be adding many <br> tags (sometimes > 20) leading to a huge amount of space from the title in the comment (line 1) after all the <br>'s the table is way down below.
It seems to work normally with other HTML tags, but seems to have a problem with <table>'s specifically. I've been trying to remove the excess <br> tags but haven't had much luck, so am filing this bug report.
The text was updated successfully, but these errors were encountered:
Thanks. Just to add, i tried putting the table into a string-variable and passed the output to "Add comment to incident (V3)" and it does exactly the same thing (i noticed it passes HTML colors across from the <table> tag, but it strips it out when the html is put into Add comment to incident (V3) directly).
I've tried trim(variable('mystring')) to ensure there's no leading or trailing whitespace, and see the same.
I need to transpose the column headers from the top to the left, hence the reason i'm not using "Create HTML Table".
Describe the bug
In a Logic App, using the Sentinel logic-app connector (Add comment to incident (V3)) in a For Each loop and entering a simple HTML table as the comment causes the table to be prefixed by many
<br>
tags upon presentation inside the browser leading to an unprofessional looking comment.To Reproduce
Steps to reproduce the behavior:
Expected behavior
A comment with a title, a newline, then the table presented graphically (without excessive newlines between title and table)
Desktop (please complete the following information):
Additional context
Using Chromes "inspect" feature to inspect the HTML in the relevant comment, expanding the relevant
<div>
, Sentinel seems to be adding many<br>
tags (sometimes > 20) leading to a huge amount of space from the title in the comment (line 1) after all the<br>
's the table is way down below.It seems to work normally with other HTML tags, but seems to have a problem with
<table>
's specifically. I've been trying to remove the excess<br>
tags but haven't had much luck, so am filing this bug report.The text was updated successfully, but these errors were encountered: