DECEMBER 19, 2017 ~ NICOLE PRESTBY I had a requirement from a client recently to show all list item attachments on the various task forms in an approval process – which, if you think about it, makes total sense. With any project, we always have a common goal of making the user experience as seamless as possible for our users and approvers. So, why wouldn’t we provide all pertinent information needed (including related documents) to complete the requested review and approval, right there on the task form? I found a post on Nintex Connect which walks through meeting this requirement by leveraging a custom action created by Nintex Technical Evangelist, Vadim Tabakman . But, what if you don’t have access to deploy a custom action to your SharePoint environment? In this case, I actually didn’t have access to the client’s server. So, I decided to come up with a solution that would produce a similar outcome, without the...
Background A common requirement among form designers is the ability to surface SharePoint data from another list and optionally process that data. Displaying an entire list item or a list view is possible with the List Item and List View controls respectively, however the aforementioned controls render html as their output which cannot be processed in a Nintex formula. In scenarios where you want to obtain a value from a list column, for display or processing in a formula, the lookup function is a viable approach. An example would be a purchase order form whose list of purchasable items is maintained in a central list within SharePoint. Henceforth is an example of how to use the Lookup function. A Purchase Order utilizing the Lookup function Given a Products list containing the following purchasable items: We want to create a Nintex form allowing a user to purchase items from a centralized list. The first step is to create our Nintex Form with a Lookup control that is c...
Introduction When versioning is turned on for a SharePoint list or document library, there are times when you may need to report on the number of list item versions, or delete versions that exceed a threshold. These scenarios can happen if; 1. Version limits (for the maximum number of major/minor versions) were not set, and the list has too many versions 2. Version limits are being applied or reduced, and you need to retrospectively delete all the versions in a list that exceed the new threshold* 3. You are performing an upgrade, and you want to prune the versions of pages in the pages library (on a publishing site) 4. You want to run a report to determine how many items in a list have more than "x" number of versions *When the version settings are changed on a list, existing versions on existing items in the list are not changed until the item is modified. Therefore, if you reduce the maximum number of versions to be kept for items in a list, the changes only take effec...
Comments
Post a Comment