Changing a SharePoint List or Document Library

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. K2 detects SharePoint list or library changes and displays a warning 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 let K2 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 a K2 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

K2 checks the SharePoint item 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

The Create K2 Application page will display a warning message in the Data section if K2 detects unsupported fields in the list/library.

Similarly, a warning displays in the Form Section if K2 supports a SharePoint Field at the SmartObject level but not at the Form level (Managed Metadata Fields, for example). You can still generate and use the Form, but K2 will not generate controls for the unsupported Fields on the generated Form.

For unsupported lists and libraries (for example a Data Connection Library), K2 does not create a SmartObject nor the associated Forms and Views. For these unsupported lists and libraries, the Create K2 Application page will display an error message and prevent you from creating any artifacts, as shown below.

For more information see Supported Artifacts.