Symptoms

When editing the "Edit List/Library name] View" via the K2 for SharePoint app, adding an extra column to the right in the layout table seems to corrupt the formatting options of the layout table, preventing the user from effectively editing columns in rows in the layout table housing the view configuration and controls.
 

Diagnoses

There are two issues here:
1. The default views created when appifying a list or library with Appit/K2 blackpearl for SharePoint seem to create the edit view with improper settings, causing this to happen when another column is added. The improper formatting is that there is an invalid colspan for the new column after it is added, which then prevents the options to edit the column/new cells from being revealed to the user.
2. The smartforms infrastructure that works to prevent invalid actions (like creating a column with an invalid colspan) does not seem to be firing properly for this action, having taken place on a view with improper architecture.

To reproduce the issue prior to the latest Appit update, and on current version of K2 blackpearl for SharePoint (latest being 4.6.11 at the time this KB was published):

1. Create a custom list in O365
2. Register SmartObjects and Forms against the list using Appit/K2 blackpearl for SharePoint
3. From the K2 Artifacts page on the list, right-click the Edit view and choose "Edit"
4. Click on any of the right cells, then click the toolbar button near the top to create a column to the right
5. Double check that the formatting options are available and working for any of the cells in the table
 

Resolution

This can be worked around by first creating a new layout table to move the existing controls to in the broken view, and then by editing the view directly from the K2 designer link (not by clicking "Edit" on the affected view from the K2 artifacts page for the list or library)and running the developer tools in chrome, and paste the following into the console after selecting one of the affected cells:

$("#bodySection .editor-table").eq(0).find("andgttbodyandgttr").each(function(index,row){if(indexandgt0){$(row).remove

Essentially, this truncates the problem layout table and restores the functionality of that cell that's left to the user at design time. This temporary fix does not prevent the issue from happening again, however.

This was fixed in the latest update of Appit, but may still be encountered in K2 blackpearl 4.6.11.

The latest fix pushed to Appit will prevent the problem from happening again on the view where the behavior was originally seen, as well as all future views created via Appit for lists and libraries.

If you would like assistance with this workaround or have additional questions about the behavior, please feel to contact K2 Support.