I’m in the middle of preparing a demo of Nintex Forms on our SharePoint 2013 clients. I’m using their trial demo for Nintex Forms at this point–but I’m pretty sure there will be buy in.
One thing I can’t seem to remember about OOTB SharePoint Input forms is how do you prevent fields appearing on the Input Form without resorting to Content Types.
For example, let’s say you create an App and use the Contacts Template. Is there any easy way to limit the input fields? Lets say you don’t want the Address, City, State, Zip, County fields in the list. You also don’t want your users to have to scroll through all the junk.
One more complication for this client, they are using the Standard Version of SharePoint so InfoPath (Customize Form) is NOT an option.
Is there any easy way for a regular user to accomplish this–someone without access to SharePoint Designer.
thanks,
Stephan
Thanks Drew. I am aware of customizations that can be made with jQuery–but the point here is to empower the “average user”. A user that may be more concerned with getting data into the form and not know anything about jQuery.
This is where I think Nintex excels. It is quite easy in Nintex to hide a field with just a smidgen of logic. Plus the “drag n drop” features of just arranging the form can become very routine so that most information workers can easily gain proficiency.
Of course, someone has to pay for the Nintex Form library. An additional selling point is that Nintex Workflows and Nintex Forms will work on the Standard Edition of SharePoint.
Thanks, Keith. I’d love to see the PowerShell examples as a developer.
However, I’m trying to enable users not to need a developer. The average “Joe User” is not familiar with PowerShell–or would we want them to be familiar with it.
You can customize the NewForm.aspx and EditForm.aspx pages directly and use any combination of JS or CSS to adjust what the user sees. This can include the hiding of fields.
I have a sample code that is used in Powershell to hide fields when a new item is created. I’m not a code kind of person, but it’s simple enough to do. Send me a message if you want it.
Thanks Paul. I didn’t want to do an unfair comparison. OOTB Input forms are not really user-friendly for extensive customization. This is why I’m excited about the Nintex Forms. Even though I work for NASA in Huntsville, I don’t want our user to have to user rocket science to hide form fields.
