Changing a SharePoint List or Document Library

From Nintex Automation (5.7) onwards there are two different apps for SharePoint. The legacy Nintex K2 for SharePoint: used for SharePoint on-premises and upgraded environments for SharePoint Online, and Nintex Automation for SharePoint: used on new installations for SharePoint Online.

When a list or library changes (such as adding a new column, or changing the list or library name), and application elements such as SmartObjects or forms were previously generated for that list or library, you must update the associated SmartObjects, and potentially the views, forms, and workflows as well. SharePoint list or library changes are detected and a warning displayed like 'Warning: the library and SmartObject are out of sync' on the K2 Application page. This warning provides links that can automatically update the generated artifacts for the list/library by regenerating the SmartObjects, views, and forms. Click the appropriate link to regenerate only the SmartObjects, or the SmartObjects, views, and forms.


  • When regenerating customized views and forms, any customizations to those items will be lost.
  • If you are using the generated SmartObjects in a workflow, in a SmartForm or in code outside of the SharePoint application's generated elements, you may also need to update those items manually to handle the changes to the SmartObject.

You may also see this warning when you have deployed an application to a target list/library with a structure different to the source list/library. In some cases you may be able to safely ignore this message. See the KB article KB002528: Known Issue: "The list and SmartObject are out of sync" warning message when Viewing List or Library Artifacts for more information.

Criteria

The SharePoint item is checked for changes that would impact a SmartObject property or method, such as:

  • adding or removing a column
  • modifying a column's type (changing from text to number, for example)
  • the maximum value of a number field
  • scope (for people and group fields)
  • adding a content type (which means methods need to be added to the SmartObjects)
  • changing the list or library name