Skip navigation
All Places > Getting Started > Blog > Authors bburke

Getting Started

5 Posts authored by: bburke

Date Stamp a Repeating Control

Posted by bburke Aug 23, 2016

I had a lot of difficulty placing a date stamp on a repeating section entry.

aditya gandhe presented a solution Repeating Conrol + Current user Name + Time that included Current User and Time but it was more than I needed.


With some help from my colleagues on our development team, I'll document how we date stamped multiple repeating section entries.


First, on our form we placed a repeating section, inside that control we place a date/time control.


In the properties of the date/time control we set the Default Value to "blank" and Date Only to "Yes".


In the properties of the Multiline Textbox nested in the Repeating Section  create a control named "control-class" (of course you can name it what you want).

Ensure you connect the repeating section to a list column.


In the form settings, insert the following in the Custom JavaScript section:



NWF$(".control-class").on('change', function(e) {

var timestamp = new Date();





Publish your form. If you enter text in the repeating section multiline textbox, the date/time control will not update until the focus changes to somewhere outside the multiline textbox.


This includes: If the user enters text in the multiline textbox, leaves the focus there and selects "Save", the focus will change and the date stamp will be saved to the form.


Additionally, if the multiline textbox is modified, it will update the date/time control.


Hopefully this will be useful to you somewhere down the line.

Recently, I was asked to hide the "Cancel" button on a Nintex Form.


Using the Internet Explorer Development Tools (F12), I identified the Cancel button element.




It was necessary for me to use the element id (because the class is used multiple times in the form), so I inserted the following to CSS on the form.


#Nintex.Forms.SharePoint.Ribbon.Filler.d22208f1_d79c_450b_a0dc_aadff6857888-Large {




Unfortunately this didn't work.


After some research I realized the periods in the element id name are not recognized by CSS and need to be escaped.
Adding a slash (\) in front of each period did the trick.


#Nintex\.Forms\.SharePoint\.Ribbon\.Filler\.d22208f1_d79c_450b_a0dc_aadff6857888-Large {





I jumped right in to building a form... I got this!


I plugged away adding items as fast as I could and before I knew it I had a decent size form put together.


Time to run it! Well. yeah my layout in the forms designer looked a whole lot better than in runtime.

Controls were overlapping, pushed to the left, pushed to the right........ When applying rules especially hiding and showing items would totally shift items at will.


I got some great support from Nintex after many hours of struggling to get the form to behave the way I wanted it to.

Bottom line: Panels


Avoid just dropping items on a form. Use panels to group your form elements into logical sections.

Here's an example of how Panels helped solve a problem:


I applied a rule that would hide the text seen below after a date was entered into the form. Just laying the controls on the form, when the rule executed, the remaining controls would shift and end up on top of each other. 

By adding a Panel to my form and I placed all of the controls inside the panel, the rule executed and the layout behaved as expected.


If you find yourself having issues with your layout shifting at runtime or after applying a rule, consider Panels.


Tips for Newbies (like me)

Posted by bburke Aug 13, 2016

I have always wanted Nintex Forms and Workflow for many years now. It's been about 3 months since I was able to purchase the Enterprise Edition and it has changed how I support my customers. Like anything else, learning new apps can be exciting and frustrating. As long as I can remember I said to myself "this would be a good lesson to share..." but I'm always just focusing on my work and always forget to follow through. This time I'll give it my best shot because 'm loving working with Nintex.


I want to share with other new users things I find along the way that will help either get over that obstacle they face or bring to light a different approach. I'll be adding items as I progress through my Nintex journey.


Nintex Workflow

Action Sets


Nintex Forms

Hide Individual Ribbon Elements

Date Stamp a Repeating Control (* recently added)






Date and Time Format Strings - Quick Reference Guide - Andrew Glasser (* recently added)

Nintex Community Training Space - (must bookmark)

Need to Hide the Ribbon on your Form? - Daniel Stoll

Rules Examples for Nintex Forms - Nick Hurst

Nintex 60-second Solution Scenarios - (getting that idea started)

Nintex Forms for SharePoint How-to Videos

I started creating my workflows in a very linear fashion across or down, each action laid out on my canvas.

I quickly discovered the ability to "label" my action panels (do it!)

But as my workflow started to grow in size scrolling up and down and side-to-side was increasingly frustrating. The only way I could get a clear view of the entire workflow was to zoom out which then made my label very hard to read. Testing my workflow also became very time-consuming as I would have restart and run through 10 steps to get to the action I thought was causing the problem, you get the idea.



One day I discovered Nintex in a Minute, Nancy & Shelley, Forms Film Festival, Jeopardy and Secret Agent Ninja in the Training Blog. This is a must bookmark, especially if your just starting out.


Workflow actions for 2013: Action Set  by Kayla Marsden gave me my first exposure to Action Sets, enough to want more.

A Google search led me to a Nintex Tips and Tricks video by GigWerks.


These two references pointed out that I could group my actions into containers and achieve the following:


Below shows a workflow on the right without Action Sets. Each step laid out on my canvas. A similar workflow on the left using Action Sets.



With the Action Set, I am able group the actions into logical steps of the workflow and collapse the Action Set so I can easily visualize multiple steps in the workflow in one view, no scrolling or panning.




The Action Set allows you to expand or collapse the group of actions by selecting "Minimize" or "Maximize"



This made it much easier for me to lay out, label and visualize my workflow making development a more pleasurable experience.


As I said, as the workflow became larger in size it became increasingly difficult to pinpoint errors during testing.

Notice in the Action Set menu above, there is a selection named "Disable". This selection is a testing bonus!


Below I have disabled the first three Action Sets. When I publish and run the workflow, it disregards those actions and in this case starts with "CPO for Signature Action Set.



So if your workflow contains many, many actions, this could be an incredible time saver, relieving you of having to go through multiple steps to get to one specific step when testing.


I would encourage you to take a look at Action Sets now and utilize them as a routine in your development process.

Filter Blog

By date: By tag: