Tuesday, May 2, 2017

Getting i:0#.w| as a prefix in emails In Nintex Workflow for sharePoint 2013

Getting i:0#.w| as a prefix in emails In Nintex Workflow for SharePoint 2013

I am using SharePoint 2013 and Nintex workflow.  When any email is received through Nintex workflow, the People names are displaying like this : i:0#.w|domain\name..

1. To fix this issue, you would need to create a "Workflow variable" of  type "Single Line of text".

2. After that add a new action of "Regular Expression" from "Insert Action" > "Operations" > "Regular Expression" before any " Send notification" Step.

3. Now Configure this "Regular Expression" Action.

The pattern which you have to use is : i:0#.w[|]

You need to specify name of "workflow variable" in "Store Result In" Section  which you created in step 1.

After that you can use the same variable in "Email Notification" Configuration Section.

 Now the full Name would be displayed of the Person.

Friday, March 17, 2017

Configuration Error : web.config ConfiSource

Everything on my end was working fine and suddenly I faced this issue while hitting my SharePoint Application. This was the below error which I was getting while hitting the app.

After going through some of the forums I got to know that one extra line has been added somehow in <appSettings> for key. When I removed this line, I was able to hit my application without any issue.

<appSettings configSource="AppSettings.config">
<add key="aspnet:UseStrictParserRegex" value="true" />

<appSettings configSource="AppSettings.config">

Friday, December 30, 2016

SharePoint 2013 Search Provisioning

SharePoint 2013 Search Provisioning

 SharePoint 2013 Search Overview

In SharePoint 2013, there are numerous components in Search Topology:
  • Search Admin Component
  • Index
  • Crawler
  • Content Processor
  • Analytics Processor
  • Query Processor

Enterprise Search Life Cycle

Content Processing

Analytics Processing

Planning and Deployment

Farm Configuration Wizard - Pros/Cons

Central Provisioning  - Pros/Cons

PowerShell Provisioning  - Pros/Cons