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

To Update manage metadata column in SharePoint list we need two thing:

1. Label of manage metadata

2. Term ID of the manage metadata.

Scenario: I want to update "Europe" in manage metadata column in SharePoint List. I have only label with me which is present in Team store.But I cannot update manage metadata column directly using action "Update Item" as I also need the termid for same.


1.We have to first select the termsetID from which the "termid" need to be taken and save in variable

example: "Country" is TermSet and need to get its ID from "Term Store management".

2.Using Taxonomy webservices "<siteurl>_vti_bin/TaxonomyClientService.asmx" in Action "CallWebservices" and user Method as "GetTermsByLabel"

Once we get the SOAP Editor details , modify the below Web Service as :



3. We get Result in XML then using "Query XML" get the TermID based on the TermStoreID


4. Once we get the TermID and the update list item using "UpdateListItem" with "label | TermID"

example: "Europe|TermID"

I was asked to create a workflow to send a reminder email to all the manager's that have time cards yet to be reviewed by them. I want to send only one email, even if they had more than one time card to review. 

This is a SITE workflow. This way I can schedule it to run when I want. You can schedule it to run at what ever interval you desire. List or Library workflows work best when set up to run when something is created or modified.


First set up your variables. 


This is what my workflow looks like. 


Configure your first query: I filtered by the status of Submitted as they are ready for review but not yet reviewed.

Select your "Collection" variable.


Next, use a Collection operation to remove the duplicates


Configure the For each


Next we want set a variable to find the Manager's User ID so we can filter it later. 


We will query this list again. This time filtering so the list Column (manager) and the Variable match up.


Now I want to send a notice to each manager based on this query.


You can use this on a task list, workflow task list, or just about any list or library that has a people picker and choice column.


I hope you find this useful!

I was asked to come up with a way to show how long a discrepancy went uncorrected once the department was notified.


This was on an inspection list (named Field Audit List). 

These are the columns I used in the SITE workflow: 

Status (Choice: corrected and needs correction as choices)

Audit Date (Date)

Submitted to Dept (Date)

Date Corrected (Date)

Days Outstanding (Number)


There are a few more columns, but these are the ones I used in the workflow. I scheduled the SITE workflow to run daily. Each day the Days Outstanding is updated with the number of days since the item was submitted to the Department with no update in status of Corrected. This is a filtered view of only those still needing correction.


In my scenario, I used Nintex to loop through the list and each item to calculate the number of days from the date it was submitted to the department to the current date without correction. 

The workflow variables and types are:

The name of my list is Field Audit List. It made sense to me when I set it up.

Here are the steps included in the workflow and how I configured them.



Query List: FA_List is from the variables I set up (collection type)



For Each: FA_ListID is from the variables I set up (list item ID type)


Set Variable: Set the DateSubmitted (date variable) the same as the Submitted to Dept (date column from list) when the ID equals the Workflow Data FA_ListID. This way they correlate to each other.


Build String: Click in the box, then click Insert Reference.



Click on Inline Functions, double click DateDiffDays

Put your cursor between the (), then click on Workflow Variables - double click DateSubmitted to add it.

Put your cursor between the }), add a comma (,)

Click on Common - double click on Current Date


The formula should look like: 

Insert Reference




Set Variable: Since my Days Outstanding is a number column I set the FA_Number (number) equal to the FA_DateDiff (text) so the number would display correctly. I believe you could save this step by changing your column to text and it may still work appropriately. I haven't tested it this way though.


Update Item: Now I update the Days outstanding with the FA_Number.


Now save and publish your workflow and schedule it to run daily. I recommend setting it to run during non business hours as to not tie up your server, although it isn't too complex of a workflow.



I've attached the workflow as an example.


I am trying to create a cascading drop down in Nintex Form, but the filtering by a control’s value its not working (the filter works by a specified value).

The control works perfectly on our site, but not at the site of a customer.


This is the XML error that occurs when the page loads


<?xml version="1.0" encoding="utf-8"?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "">

<html xmlns="">


    <title>Request Error</title>

    <style>BODY { color: #000000; background-color: white; font-family: Verdana; margin-left: 0px; margin-top: 0px; } #content { margin-left: 30px; font-size: .70em; padding-bottom: 2em; } A:link { color: #336699; font-weight: bold; text-decoration: underline; } A:visited { color: #6699cc; font-weight: bold; text-decoration: underline; } A:active { color: #336699; font-weight: bold; text-decoration: underline; } .heading1 { background-color: #003366; border-bottom: #336699 6px solid; color: #ffffff; font-family: Tahoma; font-size: 26px; font-weight: normal;margin: 0em 0em 10px -20px; padding-bottom: 8px; padding-left: 30px;padding-top: 16px;} pre { font-size:small; background-color: #e5e5cc; padding: 5px; font-family: Courier New; margin-top: 0px; border: 1px #f0f0e0 solid; white-space: pre-wrap; white-space: -pre-wrap; word-wrap: break-word; } table { border-collapse: collapse; border-spacing: 0px; font-family: Verdana;} table th { border-right: 2px white solid; border-bottom: 2px white solid; font-weight: bold; background-color: #cecf9c;} table td { border-right: 2px white solid; border-bottom: 2px white solid; background-color: #e5e5cc;}</style>



    <div id="content">

      <p class="heading1">Request Error</p>

      <p>The server encountered an error processing the request. The exception message is 'Object reference not set to an instance of an object.'. See server logs for more details. The exception stack trace is: </p>

      <p>   at Nintex.Forms.SharePoint.WebControls.MultiLookupControlV1.Filter(String fieldName, Object value)

   at Nintex.Forms.SharePoint.FormControls.SharePointLookupFormControl.&lt;GetDataValuesToRender&gt;d__4.MoveNext()

   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()

   at System.Linq.Buffer`1..ctor(IEnumerable`1 source)

   at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)

   at Nintex.Forms.SharePoint.FormControls.BaseDataAccessFormControl.GetDataValuesToRenderAsString(FormControlProperties controlProperties, String contextData)

   at Nintex.Forms.SharePoint.FormControls.SharePointLookupFormControl.GetControlData(String controlProperties, String contextData)

   at Nintex.Forms.SharePoint.Services.NfWcfService.GetDataForControlAsync(GetDataBody body)

  at SyncInvokeGetDataForControlAsync(Object , Object[] , Object[] )

   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]&amp; outputs)

   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc&amp; rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc&amp; rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc&amp; rpc)

   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)</p>






Can anyone provide some insight to this issue?




Just follow the next steps.


  • Open Nintex form
  • Select Code







Push the button

Posted by rbachmann Champion Oct 11, 2016

So, we all know that it is possible to start a workflow externally. (Thanks to Eric Harris Externally start Nintex workflows in seconds with Zapier!)

The other day I was thinking of: How cool would it be, to start a workflow with a proper button?

After a short research, I ordered two buttons from They are fully supported by Zapier so in no time I had my first (by a button startable) workflow. 



Ok, geek stuff. But what can they be used for in a real life scenario?


I am thinking of task list, where new tasks aren't assigned to anyone. With one push, a workflow assigns a task to the initiator.

Or let's assume you have a single site-workflow to terminate several different workflows. One push and you are done. (You probably use a big red button for that right!?)


I know there are some really creative community members out there. Please share your ideas with me! I am curious to know what you would automate with just one button.

Over the last couple weeks, a few customers have asked how to access the Nintex Live actions for O365. Here is a short tutorial on how to do so. 


What is Nintex Live?


Workflow action that uses the Nintex Live service. Connects to an internet-based application exposing web service APIs for public or contracted consumption. Examples: Google Drive download file, Dropbox query files.


How do you access Live actions on O365?

To add actions to your toolbox from the Nintex Store

  1. In the Nintex Workflow designer, click Store in the ribbon.


    For instructions on accessing Nintex Workflow designer, see Accessing the Nintex Workflow designer.

  3. the Nintex Workflow designer.htmThe Nintex Store dialog box appears.

  4. Search and browse: 
    • To search for an action or pack, type in the search box and then press ENTER.
    • To browse packs, click the categories under the search box. Clicking a category filters the display.
    • To display the actions in a pack, click the pack.
  5. On the action or pack of interest, click Add or Try (for information on trialing an action, see the following section).

    The added actions are now available in the Actions toolbox of the Nintex Workflow designer for use in your workflows. 





Currently in Nintex Forms for Office 365 you cannot open old form versions as you can on the on-premise version.

While we wait for this feature I want to share how me and my team work with forms while we are sharing it.

We opened on the designer the same form with different users (User1 and User2) and made changes and then User1 published changes and then User2 published the other changes.

Finally we saw that the last published form is the current version without the User1 's changes.

Although we imagined that result, the Nintex designer does not show any message for the form opened at the same time or that another user made changes.


With that said, we decided to implement a simple idea that is helping us without losing changes of another designer/developer/user on the form design.


The simple idea is:


- Add a label on the right upper corner of the form

-When the form is opened by an user, we set the convention to edit that label and set it with something like this: "I am User1 and started editing the form at 3.00 PM, please donot make changes" and save the form.


So if another user edits it , he/she will see that label, and will not save/publish the form.

Still using Lotus Notes? Interested in Migrating to SharePoint? Watch my (Dean Virag) interview with Brad Orluk to learn more about why companies are wanting to migrate away from Lotus Notes, obstacles in migrating form Lotus Notes, tools to help migrate, and so much more..


Filter Blog

By date: By tag: