Package and Deployment - Deploy package fails with 'The package is missing at least one SharePoint related item required to successfully deploy'

  • 24 February 2022
  • 0 replies
  • 6 views





 








Package and Deployment - Deploy package fails with 'The package is missing at least one SharePoint related item required to successfully deploy'



























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



The following error occurs when attempting to deploy a Package using the K2 Cloud Package and Deployment Tool:



 



“The package is missing at least one SharePoint related item required to successfully deploy. This is most likely the result of having manually removed either the list or library SmartObject, service object or workflow”



 



If you click on "OK" the P&D tool closes.



Image



Symptoms



This is caused by the SmartObject name in the [Integration].[ProcessSharePointSetting] table not having a corresponding entry in the [SmartBroker].[SmartObject] table.



To confirm, run the following SQL statement. Please remember to fill in the variables for 'LIST_NAME" and 'SYSTEM_NAME_FROM_PREVIOUS_QUERY':





SELECT * FROM [Integration].[ProcessSharePointSetting]
WHERE [SmartObjectName] like '%LIST_NAME%'



 



SELECT * FROM [SmartBroker].[SmartObject]
WHERE [Name] = 'SYSTEM_NAME_FROM_PREVIOUS_QUERY'





 



 



 



 



Troubleshooting Steps



If the second query does not return any results, it might be due to SharePoint site name changes, and proper SmartObject clean up steps not being followed.



When searching in the [SmartBroker].[SmartObject] table, you might find duplicate entries as follows:



support_sharepoint_com___sites___k2appit_SharePoint_Lists_CustomList



support_sharepoint_com___sites___k2appit_SPSite_Lists_CustomList



If this is the case where the ProcessSharePointSetting table is pointing to the incorrect SmartObject, please log a Support Ticket for support to investigate.



 



The issue could appears too if you don't have all columns of the origin environnement in the destination environnement.



Example of column name that could appear/disappear according the SharePoint version:



ExtractedText

KeyPoints

Tags

KeyPoints_MediaServiceKeyPoints_

Tags_MediaServiceAutoTags0

MediaServiceAutoTags

MediaServiceKeyPoints

MediaServiceOCR







0 replies

Be the first to reply!

Reply