Skip navigation
All Places > Getting Started > Blog > 2015 > October

Applies to Nintex Workflow 2010 Nintex Workflow 2013



If you have a list where a new workflow does not create a status column while another list does.



In most cases this is a setting for your Web Application for List View Lookup Threshold.  By default in SharePoint it is set to 8, so if you have more than 8 lookup type columns such as (Person/Group, Workflow Status or Managed Metadata), then if you add any other lookup will not show up on your list view.  However, you can change this default to accommodate higher number of lookup columns for your lists in Central Administration.



When you change this setting to more than 8, on the SQL side it goes from a record lock to a table lock (processing more than 8 joins in a single transaction).


This can have a major impact on the farm especially if the list is being viewed by multiple users because the tables in the SP content database are being locked during the time the page is being loaded. While the table(s) are locked, no one else can use them until the previous transaction has been completed. This means that when user 2-3-4-5 goes to view the list they will see the “Working on it” spinning wheel until the page has been loaded by the previous user.


Please consider the impacts this will introduce before changing any settings on Web Applications.


To see the current List View Lookup Threshold value, go to Central Administration > Manage Web Applications, click on your web application and select Resource Throttling from the General Settings ribbon drop down:

The default List View Lookup Threshold is set to 8.

Here you can adjust to a value that suits your needs, be aware there are reasons for limiting Lookup columns and caution should be used when changing these settings.


WARNING!!! This is not recommended as a solution, only if absolutely a must.  See:

Applies to Nintex Forms Enterprise 2010 and Nintex Forms Enterprise 2013




In rare cases when you are applying an Enterprise key to your Nintex Forms you see this error: “This feature is only available in Nintex Workflow Enterprise Edition”.




The cause of the issue is a piece of vestigial code present in the Nintex Forms product since its first release around licensing. When the product doesn’t recognize the license type, like our previous versions of Forms not recognizing the new Enterprise licenses, it defaults to this code and displays the Nintex Workflow Enterprise error message.  Unfortunately as this code is in all builds of Forms already, there is no way of easily patching the issue without upgrading to latest version of Forms.



You will need to take the following steps to get the feature to be added to Central Admin and resolve the license issue. This does mean that you will have to upgrade Forms on your Farm to the latest version.

To use a Nintex Forms Enterprise license, you must be on Nintex Forms 2010 1.9 or Nintex Forms 2013 2.7 or greater.

Please Note: The International versions of Nintex Forms Enterprise is not yet available. We are currently working on this and hope to have it in the near future.


How to upgrade to Enterprise Forms:

  1. Contact Nintex at to obtain a temporary Forms Standard License and new Forms Enterprise Forms license.
  2. Import the Standard License in Central Administration.
  3. Performs an IIS Reset.
  4. Upgrade to either Nintex Forms 2010 1.9 +  / Nintex Forms 2013 2.7 +.
  5. Once the latest version has successfully been installed, import the NEW Enterprise Forms License.
  6. Perform final IIS Reset, this is the 2nd one in this process.
  7. Enterprise Forms functionality should now be enabled in Central Admin and no license error.


Just like to share my experience with Nintex Forms rules and comparison of the 'Current User' common context data against person columns.


What I was trying to do was to hide an 'acknowledgement' button (just a standard button which is connected to a field to record a value on the form submit.

The form I have a leave request form and there is a person column called 'Requested For'.

After the form is lodged it sent to their manager for acknowledgement. (This is not a workflow task just a list form item)

The Acknowledgement button needs to be hidden from the user who it is requested for.


I tried to create a rule of current user==Requested For (from item properties)

However this did not work.

What happens is that the current user return the claims windows username identity.

Whereas the Item Properties person column returns the Display name of the user.


I next tried a hidden calculated value control to do a user profile lookup of the current user and return their display name (PreferredName)

However this did not work well.


Finally doing a comparison of the 'Current User' against the named control person-RequestFor worked.

I was able to confirm the value of the person control by adding a calculated value control on the form where the function = named control person-RequestFor

From that I was confirm that both calculated controls returned the claims windows username identity.


Hopefully this helps some others out there enjoying the fun of person columns.

Nintex Forms Enterprise Edition


This tutorial walks through steps to retrieve country and city data from a SQL Server database and filter the returned city data based on the selected country.

Figure: Example of a form listing cities for the selected country; if another country is selected, the list of cities is updated.



  • Database table "Cities" containing two columns: Country and City
  • Secure Store target application ID for credentials to the SQL Server database
    For more information on Secure Store, see the Microsoft article Configure the Secure Store Service in SharePoint 2013.
  • List columns for binding the value and display fields for each instance of the SQL Request control (optional)



  1. Add the SQL Request form control for "Country" and apply the following configuration.
    Display formatDrop down list
    Query typeSQL

    SELECT [Country]

    FROM [CrestanDemoData].[dbo].[Countries]

  2. Add the SQL Request form control for "City" and apply the following configuration.
    Note: Red text indicates inserted references.
    Display formatDrop down list
    Query typeSQL

    SELECT [City]

    FROM [CrestanDemoData].dbo].[Cities]

    WHERE Country='Country'

    To insert a reference to the "Country" control, select it from Named Controls in the Insert Reference dialog box.
  3. Publish the form and you're done!

Nintex Forms Enterprise Edition


This tutorial walks through steps to display current wind direction for the city selected on the form. The tutorial uses the Web Request form control from Nintex Forms Enterprise Edition to send a GET request to the Yahoo weather API (anonymous authentication), filtering based on the city selected on the form (ChoiceField).


Figure: Example of a form displaying wind direction for London; if another city is selected, the wind direction is updated for that city.



  • List column WindDirectionID for binding the XPath value field
  • List column WindDirectionText for binding the XPath display field
  • Choice control “ChoiceField” with valid values for cities referenced by the API (example follows)
    • Casablanca
    • London
    • Melbourne
    • Paris


Once you have the above prerequisites, add the Web Request form control to the form and apply the following configuration. Publish the form and you're done!

Note: Red text indicates inserted references.








ID connected to



Text connected to



Display format



Service URL wind from weather.forecast where woeid in (select woeid from geo.places(1) where text='ChoiceField')&format=json

To insert a reference to ChoiceField, select it from Named Controls in the Insert Reference dialog box.

Request method



Authentication type



XPath for display



Nintex Forms 2010, Nintex Forms 2013


If you are using any of these list templates, you will notice that the Nintex Forms button is grayed out.  This is due to how the list template is generated in SharePoint and these are not supported by Nintex Forms.


Designing custom list forms for the following is not supported:


  • Nintex Workflow content types
  • Document Sets
  • Blog Post
  • Blog Comment
  • Discussion List
  • Survey
  • InfoPath Form Library
  • SlideShow
  • Event (not calendar event) Content Type (designer still enabled)
  • Reservations (designer still enabled)
  • Schedule (designer still enabled)
  • Custom List Templates


In addition these List Templates IDs are not supported due to how SharePoint generates them:


  • 115 - XML Form library
  • 120 - Custom grid for a list
  • 108 - Discussion board
  • 301 - Posts (Blog)
  • 302 - Comments (Blog)
  • 303 - Categories (Blog)
  • 2100 - PowerPoint Slide Library
  • 10000 - Custom List Templates


See a complete listing for 2010/2013 list templates here:

To show a guide to fill in complex forms, a tool tip is often not enough. Formatted instructions may be displayed in a separate dialog by clicking on an info button:


It's a floating window that contains a title bar and a content area. The dialog window can be moved, resized and closed with the 'x' icon by default or by pressing escape key.


How can that be done in Nintex Forms?


First of all create an info button:

I used File:Information green.svg - Wikimedia Commons as button image.


Here is the client click coding:



    title: "Topic 1",

    hide: {

        effect: "fade",

        duration: 1000


    maxHeight: 400,

    minWidth: 500,

    modal: false



Here the jquery-ui dialog widget is used to display help text. Modal behavior here is non modal, but can be changed to modal setting option modal to true.


Now create a Rich Text Control in your form and enter help text:


In control settings Visible has to be set to Yes. To hide the Control use css class, e.g. info-hidden and css in form settings: .info-hidden {visibility: hidden;}


Next step is to define the ID #Topic_1_help used in button client click coding. For that edit source of help text:

Enclose full source text with <div id="Topic_1_help">.... your help text.... </div>


That's it!

Building Nintex Mobile Apps


Building Nintex Mobile Apps


Thursday, October 22, 2015 | 1:30-2:00 pm ET

In this session we will demonstrate the value of building mobile apps utilizing Nintex Forms and Workflow. Over the 30 minute span of this webinar, we will build a live, interactive mobile app. Webinar participants will have an opportunity to access the app live and provide input. As a bonus, 2 participants that provide input will be selected at random to win a $25 Amazon Gift Card!



Presenter: Terry Simpson, Solution Architect

Hello Community again,


This time i want to share my knowledge and discovery how to build dynamic HTML 5 responsive reports from SharePoint list item.


I came up with this technique when i got a project to build a consignment process routine in SharePoint. The hardest part was how should I build a report if there is no reporting action or print form action in Nintex Forms or Wrokflows. And another problem was the Customer requirement that the report should be responsive (work in all type of screens) and in the report it's ID should be converted to barcode. So i started to think which tool deals the best with responsive design and the #1 was HTML5 and CSS3 with Twiter Bootstrap framework.

And the barcode requirement i solved with JS library BARCODE : JQUERY PLUGIN TO CREATE BARCODE ONLINE



So lets start.


1. First of all i build a list with corresponding data

All fields are single text line fields apart one which will be link to html report.


2. Build you custom form with repeating sections and all the data needed

3. Now we need to create HTML report template and put it in library (my HTML template looks like this:)

<!doctype html>

<html lang="en">


    <meta charset="UTF-8">

    <title>Sample Invoice</title>

    <link rel="stylesheet" href="">


      @import url(;

      body, h1, h2, h3, h4, h5, h6{

      font-family: 'Bree Serif', serif;



      <script src="//"></script>

      <script src="http://portal.wsy.lan/Sprendimai/vaztarasciai/HTMLTemplates/jquery-barcode.min.js"></script>



                      $("#barcode").barcode("{ID}", "code128",{barWidth:5, barHeight:50});}






    <div class="container">

      <div class="row">

        <div class="col-xs-12 text-center">

          <h2>Krovinio važtaraštis</h2>

          <h2><small>Nr #{InvoiceNr}</small></h2>



      <div class="row">

        <div class="col-xs-5 pull-left">

          <div class="panel panel-default">

            <div class="panel-heading">


   <h5><a href="#">{FromName}</a></h5>


            <div class="panel-body">


                Reg. Adresas: {FromAddress} <br>

                PVM kodas: {FromPVMCode} <br>

                Įmonės kodas: {FromCompanyCode} <br>

                Ats. asmuo: {FromResponsible} <br>

                Tel: {FromTel} <br>





        <div class="col-xs-5 pull-right text-right">

          <div class="panel panel-default">

            <div class="panel-heading">

              <h4>Prekių / Paslaugų gavėjas:</a></h4>

   <h5><a href="#">{ToName}</a></h5>


            <div class="panel-body">


                    Reg. Adresas: {ToAddress} <br>

                    PVM kodas: {ToPVMCode} <br>

                    Įmonės kodas: {ToCompanyCode} <br>

                    Ats. asmuo: {ToResponsible} <br>

                    Tel: {ToTel} <br>






      <!-- / end client details section -->

      <table class="table table-bordered">







              <h4>Prekių/paslaugų pavadinimas</h4>



              <h4>Sutarties Nr.</h4>



              <h4>Užsakymo Nr.</h4>



              <h4>Matavimo vnt.</h4>











   <table class="table table-bordered">







              <h4>Prekių/paslaugų pavadinimas</h4>



              <h4>Tikslas (remontas, eksplotavimas)</h4>



              <h4>Inventorinis Nr.</h4>








<div class="row">

    <div class="col-md-4 pull-right">

        <div class="pull-right" id="barcode"></div>





      <div class="row">

        <div class="col-md-4 col-xs-12">

          <div class="panel panel-info">

            <div class="panel-heading">

              <h4>Krovinį išvežė</h4>


            <div class="panel-body">



              <p>Pareigos: </p>           




        <div class="col-md-4 col-xs-12">

          <div class="span7">

            <div class="panel panel-info">

              <div class="panel-heading">

                <h4>Krovinį priėmė</h4>


              <div class="panel-body">



   <p>Pareigos: </p>           





  <div class="col-md-4 col-xs-12">

          <div class="span7">

            <div class="panel panel-info">

              <div class="panel-heading">

                <h4>Kontrolės tarnybos atžyma</h4>


              <div class="panel-body">



   <p>Pareigos: </p>           










Now lets look at code in lines where you see {someVariable} type text. This tags will be replaced with Nintex forms field values, so after a workflow which we will build in next step we will be able to generate dynamic HTML 5 reports.

One more thing about barcode. In line 15-19 there is a simple javascript using already mentioned jquery-barcode library which will let us to generate barcode from the form ID.


4. Building a workflow.

a) Get the repeating sections data to multiple line text variable

b) Parse repeating section fields to collections

c) Iterate through collections and dynamically build an HTML table

d) Get the template data with Web Request action GET method and save it to multi line text variable

e) Switch tags in template with fields from the form and generated HTML table

f) PUT the new generated report with Web request action into reports library


How it looks and what is important to look at:


a) in XML input parse the FormData using inline function XmlDecode


b) In this step we don't need inline function, because it is already in good format.

c) Now count one of your collections and use that count number to loop through all of them in one loop action:

In the end of the loop build you dynamic HTML table:

d) Getting the template data stream to multitext variable.

In URL address use link to the html template and request method GET.

e) Lets switch tags with RegExp actions:

f) And the last PUT the data stream through Web request action with HTTP method PUT. The URL will point to new reports library.

And the last thing is to update a link after report will be generated.


The update of the link type field uses syntax like that {URL},{Name of the link}


And the result is dynamic, responsive HTML5 report with barcode inside

Here you go. I hope it will save you a lots of time if you will bump in similar project. Why i like this technique so much is because it doesn't require expensive SSRS 2008 or other reporting tools, and is very easy achievable.


So like and share and let me know how do you liked or maybe you already had similar projects and what was your solution path.

P.S. Mine was painful but generous in terms of knowledge   I will also attach Nintex Form, workflow and report template in this post.

Hi, Everyone!


The platform on which our community is based has updated and there are a few changes you may have noticed.  I thought I should give you a quick rundown of what's new and where to find a couple of features that have moved.


First, that set of navigation links that used to be on the left side of your screen have moved to the top of the page.  That's where you'll now find "News, Recent Blog Posts, Top & Trending, Most Recent, Following and  News Stream."




The new layout shows blocks of information from the streams you either follow or updates from your Connections and Top & Trending.  If there's no activity in any of these categories, you'll see Most Recent content.




Tiles in the right pane are always visible, even when you click into one of the streams, "Recent Blog Posts, Top & Trending, Most Recent or Following."

Just be aware that the body of a News item can't be clicked, but the title is clickable and takes you to that item's page.


You can now like articles from the News stream, as you can see from the image below.




Comments are clickable and take you to the top of the comments thread on the item's page.




You can control whether you're notified from each stream using the Preferences menu under the user avatar.




These preferences now offer both email and mobile notifications. Here's what that screen looks like below.




Of course, we still want to know what you're doing!  So the Status Update is still on the site!  It's just now moved. Click any of the streams to the right of "news," and you'll see a chance to give us a shout out at the to of your screen.



It's not a complicated set of changes. And, in fact, it actually keeps the most recent content always-ready on the right side of the page. It saves you a little time by giving you the chance to "like" content w/o navigating away from your News streams.  And when you're ready to comment on a page, clicking the comment box will take you directly to to top of the comment thread on that page.


I hope you find that helpful!



Your Community Manager

Hi everyone,


Not so long ago i was asked to build a report from List which used Nintex Froms with repeating section. I thought that it is almost impossible until i found few blog posts about using XML as sub-report  data source, so i will try to show you all how simple and how powerful it can be.


1. Create a SharePoint list with Nintex Forms with repeating section. In my case i was creating Welding certificates list with information about welder and his techniques.

As you see the table below which i call WeldingProcessTable is repeating section.

2. Create a Report with Reporting Services (SSRS) i use 2008 version.

There is data source to sharepoint list and you can see a subreport in last column of the table. This subreport will point to the repeating section report which we will build in next step.


3. Now i am building a subreport called WeldingProcessTable (Just add new report item to the project):

Now for the subreport create Data source with type XML: and save it.

Now we need to add a dateset. The question which i asked my self in first place was How do i create those fields in dataset. There are 2 ways.

a) Doing it by adding all fields one by one:


b) Doing it in good IT lazy fashion Copy XML data from your repeating section column. But to be able to do that your Repeating section must be connected with list column of type Multiple lines of text. Then add this column to your view and you will be able to see XML of your repeating section:

So when you copy this XML of your repeating section add it to that data set query (<Query><XmlData><Root>{Your Repeating section XML}</Root></XmlData></Query>) and fields will be auto populated.

Next click fx button nect to the query input and replace XML with this text:

="<Query><XmlData><Root>"&Parameters!XMLData.Value &"</Root></XmlData></Query>"


Now create Parameter with name "XMLData", and you almost there.


What have you done is you created subreport with dynamic data source which will get data from parameter XMLData.


4. Edit subreport properties in main report:

Give a name and set a report as subreport like in picture above.

Then go to Parameters tab and add parameter.

In the value field select your Multiple line text field which is connected to your repeating section.

And you almost Done.


5. Last thing which took me some time to realize is when you will publish your project to SharePoint you will need to go to subreport edit his embeded datasource and set custom windows user for authentication.

Done. I hope this will help you saving some time


The tracking data for each action and task are stored in the dbo.WorkflowLog table when you have verbose logging enabled.  This allows you to see additional variable information and other details in the Workflow history page.


The “dbo.WorkflowLog” table on Nintex databases stores the verbose logging that is set per workflow. We highly recommend that you turn Verbose Logging off unless we have specifically asked you to turn it on to diagnose an issue due to the amount of system resources it consumes.


To disable verbose logging globally

1.  Go to Central Admin > Nintex Workflow Management > Global Settings and un-tick the “Enable Verbose Logging” option. This will disable the option on all current and new workflows.


To clean up the dbo.WorkflowLog tables

Open SQL Server Management Studio, connect to the Nintex Workflow databases and truncate the databases by performing the following steps:


1. Make sure that verbose logging is OFF, Central Admin > Nintex Workflow Management > Global Settings and un-tick the “Enable Verbose Logging” option.

2. Perform an IISReset

3. Restart the SharePoint Timer Service

4. Execute the following SQL command on you Nintex Databases:


USE [YourNintexDatabase]


DECLARE @return_value int

EXEC @return_value = [dbo].[PurgeVerboseLogs]
@DaysToKeep = 0

SELECT 'Return Value' = @return_value



This above command will clear all of the records from that table (should be 0 after it is finished). If anything is still trying to write to that database when you run the stored procedure, it will lock the table and anything else that is relying on it. Performing an IISreset/timer service restart will ensure that the verbose logging is truly off and help prevent this from happening.

NTX PowerShell Action - Stable Release



  • Robust security features based on Windows Remote Management.
  • Ability to execute PowerShell scripts from any machine allowing Remote Management from your SharePoint servers.
  • PowerShell exceptions are handled so workflows are unaffected.
  • OpenSource
  • Actively Developed
  • Automated Installation Routine

Planned Features

  • Async PowerShell script execution
  • Script Repository
  • Run worker as a centralized SharePoint service instead of in Workflow Infrastructure
  • Pass SPServer object to PowerShell session for determining executing server.


Current roadmap/planned features can be found here.



Disclaimer: As stated in our Terms of Use, Nintex is not responsible for any third-party content made available for download on Nintex Connect, whether or not this content has been reviewed and/or moderated by Nintex and regardless of who originated that content (including, but not limited to, Nintex employees, partners, affiliates, or moderators).  Users shall assume all risks associated with applications and other content provided on Nintex Connect.  Nintex does not provide support for any content and plugins provided for download at


NTX - Home


Source Code


Source Code (Archive)

Source Code on Github


Screen Shots




Show a form directly in the body in outlook mail.


One of out customers have a WF with a form – when the
person have filled out the form and submit in the process to the next person. He
received in outlook.

Then wanted that the form are showen directly in the
mail and not as a link.

How can they do that?

Current Nintex Projects on Codeplex



Although we have tons of features on Nintex workflows, there are also some public projects published on Codeplex that could help us adding functionalitites not available on the current actions.

Here is the current list of projects on Codeplex.



The “Execute PowerShell Script” action allows you to execute PowerShell scripts from within Nintex Workflow 2010 workflows. You MUST have Nintex Workflow.



This project is a command prompt application allowing administrator to write and run custom scripts to deploy automatically InfoPath form (with or without code) andNintex Workflow to a SharePoint server.



Nintex Workflow Analyzer is a low level workflow editor and best practices analyzer for Nintex Workflow exported files.



In many situations where we have to invoke existing .Net code. We can achieve this by using this custom Nintex action.



ALPS is a set of PowerShell scripts that extend the functionality of Nintex and SharePoint

Filter Blog

By date: By tag: