< class="prominent-subhead ">

SharePoint On-Prem 2016 VS SharePoint Online - Package and Deployment

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.
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.


Unable to deploy a SmartObject which is dependent on a SharePoint On Prem in a Document Library

An "Unsuitable item" error message appears.




SharePoint Online Libraries contain additional hidden columns (namely the Comment Count and Like Count mentioned in the error) that is not present in SharePoint 2016 On-Prem.

Due to these columns, the Package and Deployment tool cannot align the SmartObject for deployment.

SharePoint 2016


SharePoint Online



This scenario where you are deploying from SharePoint 2016 On-Prem to Sharepoint online is not supported.

The below KB is under review


Sharepoint Online has more columns on the "Document Library" than SharePoint 2016 On Prem has on the same type.

We are not able to switch off hidden fields and select which items to include and which to exclude.

The package is then created on an environment with less fields than the target environment, and this results in a mismatch.

The review of this KB will contain a

"Simple K2 Package and Deployment scenario map"

There will be a section that describes the limitations on standard SharePoint types (since we have no control over the changes made here by MS), adding that *Objects that were created via appification from a standard SharePoint template such as a document library may not work, due to inconsistent versions of SharePoint (independent of K2).