This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice This article is not considered official documentation for K2 software and is provided “as is” with no warranties.

Issue

When added a new Content Type to a SharePoint List that already has K2 Artifacts, the user is prompted to regenerate the SmartObjects, Forms and Views for the application.

Image

After Regeneration, the new Forms are fine, but on the New, Edit and Display Views the layouts has become corrupted and cannot be Edited in K2 Designer.

Symptoms

The issue will be encountered when performing the following actions:

- On a SharePint list with existing artifacts (SmartObjects, Views and Forms) the layout of a View is customised with additional columns.Image

- The SharePoint List is modified, and an additional Content Type is Added.
- After regenerating the K2 Artifacts (SmartObjects, Views and Forms), the Layout of the previously Modified View will be corrupted and cannot be saved in K2 Designer.
- An error message will display when attempting to Edit the View Layout due to a missing Cell: i.e. "The layout table is not valid at: row 1, column 3. If you have not saved the view, discard your changes and try again. If you have saved the view, undo your checkout. Otherwise contact Support."

Image

Resolution

The issue is being investigated by the K2 Developers and was identified as a bug that will be addressed in a future update to the product.

Unfortunately, there is no way to recover the View to a usable state once the error is encountered.

To avoid the issue, ensure the SharePoint Library contains all Columns and Content Types before creating the K2 Application for the first time.

The following options are available if the issue is already encountered:
Workaround 1
Create a new View and manually configure the layout. Then replace the broken View with the new View on the Form(s). Re-map any References to the Form in the associated Workflow.

Workaround 2
Delete all K2 Artifacts of the SharePoint Library and generate new K2 Artifacts.