SharePoint Designer Email HTML Format

When we create a SharePoint designer workflow with send email functionality. Email body format will not behave as expected most of the times.

Alignments will not work even though you set it to align 'top' or ‘bottom'

Solution :
The solution for that is very simple and interesting. You need to put your html code in a single line. i.e

<table>
<tr>
<td>row 1, cell 1</td>
<td>row 1, cell 2</td>
<td>row 1, cell 3</td>
</tr>
<tr>
<td>row 2, cell 1</td>
<td>row 2, cell 2</td>

<td>row 2, cell 3</td>
</tr>
</table>

This will cause alignment issue.

<table><tr><td>row 1, cell 1</td><td>row 1, cell 2</td><td>row 1, cell 3</td></tr><tr>td>row 2, cell 1</td><td>row 2, cell 2</td><td>row 2, cell 3</td></tr></table>

Above code will fix this alignment issue in Designer email format. Everything should be in one line.

Comments

Post a Comment

Popular posts from this blog

Activating a SharePoint Feature on Multiple Sites or Site Collections using PowerShell

I need to either activate or even deactivate certain features on multiple site collections. So the below script will allow you to do this.. First step create a text file in the below format, you only need to define the URL for each Site collection or site. SiteURL http://sharepointsuresh/sites/site1 http://sharepointsuresh/sites/site2 http://sharepointsuresh/sites/site3 http://sharepointsuresh/sites/site4 http://sharepointsuresh/sites/site5 http://sharepointsuresh/sites/site6 You can list all features installed on your sites by using the following PowerShell: Get-SPFeature | Sort -Property Scope,DisplayName | FT -GroupBy Scope DisplayName,Id Then use the below PowerShell Script: $SiteList = Import-Csv Sites.txt ForEach ($item in $SiteList) {             If ($item -ne $null)             {                 Write-Host "Activated Branding Feature for: $($item.SiteURL)" -...
Read more

Managed Path with WildCard and Explicit Inclusion

I thought to put an article on Managed Paths in SharePoint covering their use with Explicit Inclusion and Wildcard Inclusion and also how to use them in Real World scenarios So let’s see what Managed Path is Managed Path: By default when we create Site Collections inside a Web Application in SharePoint they are created with the URL “http://servername:portnumber/site”.  But if we want to have a specific URL other than “/site” we need to create Managed Path. So as an example if we want to create Site Collections for IT and HR Dept and want to have URL's like “http://servername:portnumber/IT” and “http://servername:portnumber/HR” we can do with the help of Managed Paths. Managed Path helps to have site collection with the URL other than “/site”. Managed Path can be created in Central Administration in Application Management under SharePoint Web Application Management. When we create Managed Path either we can select Explicit Inclusion or Wildcard Inclusion. So let’s see what ...
Read more

List All SharePoint 2010 PowerShell Commands

Use this PowerShell command to output a list of all cmdlets that are found within the SharePoint 2010 namespace: Get-Command –PSSnapin “Microsoft.SharePoint.PowerShell” | format-table name > C:\SP2010_PowerShell_Commands.txt If you would like a little more detail, then try this one: Get-Command –PSSnapin “Microsoft.SharePoint.PowerShell” | select name, definition | format-list > C:\SP2010_PowerShell_Commands.txt
Read more