Skip to main content
Nintex Community Menu Bar
Question

Why does the Send Email action reformat my tables?

  • March 21, 2025
  • 2 replies
  • 19 views
  • Translate

Forum|alt.badge.img+3

I’m migrating workflows to the Automation Cloud, and no matter if I build the table in HTML or the WYSIWIG editor, Nintex constantly messes with the formatting.  It will move whole rows to the top of the table.  The screen shot below is how the table in the email should look.


But if I have to go back into the workflow to make an edit for any reason - not even to the Send Email action this happens:


The divider rows get converted to header rows - even if I toggle that setting off or call it out as <td> instead of <th> - and then get moved to the top.

This defeats their purpose, which is to break up and organize the data.

It makes quick edits painstaking.  I don’t need a “smart” editor that actually gets it wrong every time it tries to override my actions.

If someone from Nintex could PLEASE tell me how to get around this or give us the option to shut it off, I’d be most appreciative. I build for 10+ teams and own waaay too many workflows for troubleshooting to be this time-consuming.  We moved significant portions of our work to Nintex for consistency and efficiency.  But if changes are so tedious is negates any gains for the users or me.

Did this topic help you find an answer to your question?

2 replies

Forum|alt.badge.img+9
  • Nintex Employee
  • 69 replies
  • March 21, 2025

Hi ​@karmaq 

I tried to repro this but I wasn’t getting the same result.  I’d recommend reaching out to Nintex support about the issue you’re seeing to investigate if this is tied to something in the workflow itself or if it’s a bug.  If it is a bug then they should be able to raise it to the development team.

Translate

SimonMuntz
Nintex Employee
Forum|alt.badge.img+22
  • Nintex Employee
  • 2452 replies
  • March 24, 2025

Hi ​@karmaq,

I want to add to my colleague Brent’s advice.
I have found that the rich text editors in Nintex Workflow will change the HTML code if they “think” the syntax is incorrect. I can’t 100% confirm this is a feature; it’s just an observation. For Example, if you try to use an HTML tag that is not supported, it will be removed.
To avoid this issue, I would suggest that you build your table in a variable using create a text string actions and then inserting the variable into an email.

This thread gives you an example of how to do this.
 

 

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings