Skip to main content

Hi everyone.

I have a Form template. This template extract a value from a List item thanks to a Lookup formula. This list item is rich text-ernabled.

 

On my test server, the form works fine. The content of the list item is successufly red and displayed correctly formatted.

 

On my production server, the HTML tagging of the list item is displayed in the form.

 

Test and Production servers have the same SharePoint Version, but nintex version differs. Test server runs 2.2.1.0, production server runs 2.3.4.0

 

How can I make this list item correctly formatted into my form on both of my servers?

Thanks in advance.

Romain K

Hi Romain,

 

If you would like to utilize HTML formatting in a Rich Text Notification body, you could encompass them into a Build string action and add the result to another variable.

 

You would then add this variable to the notification action.

 

The example below, shows how to display a table with a Nintex Variable:

 

<table width="100%" class="ms-rteTable-default" cellspacing="0" style="font-size: 1em">
<tbody>
<tr class="ms-rteTableHeaderRow-default">
<th class="ms-rteTableHeaderFirstCol-default">
{Workflow Variable}
</th>
<th class="ms-rteTableHeaderOddCol-default">
</th>
</tr>
<tr class="ms-rteTableOddRow-default">
<th class="ms-rteTableFirstCol-default">
</th>
<td class="ms-rteTableOddCol-default"><
/td>
</tr></tbody>
</table>

 


they need to break the HTML into two parts

 

part1 :

 

<table width="100%" class="ms-rteTable-default" cellspacing="0" style="font-size: 1em">
<tbody>
<tr class="ms-rteTableHeaderRow-default">
<th class="ms-rteTableHeaderFirstCol-default">

 


Part2:

 

</th>
<th class="ms-rteTableHeaderOddCol-default">
</th>
</tr>
<tr class="ms-rteTableOddRow-default">
<th class="ms-rteTableFirstCol-default">
</th>
<td class="ms-rteTableOddCol-default"><
/td>
</tr></tbody>
</table>

 


And then use a build string action to have Part1+ workflow variable + Part2

 

Then save this to another variable and insert it in rich text control in email body.


Reply