Deployment error with SharePoint P&D when list was re-named 

  • 16 February 2021
  • 0 replies

Userlevel 4
Badge +16


Deployment error with SharePoint P&D when list was re-named

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.


Deploying a SharePoint package errors when deploying to a list originally named with special characters and then re-named to remove those characters.

This results in object reference error on deployment of package.

Source List:

  • List named with Underscores

  • List name changed

  • List appified

  • Package created with SharePoint P&D

Target List:

  • List named with underscores

  • List name changed

  • Failure on deployment with SharePoint P&D


Deployment with SharePoint P&D results in Object Reference not sent to an instance of an object error when analyzing the list mappings if the list chosen had been renamed to remove special characters. In the example below the list was initially named: 'Test_K2_Rename' and then changed to 'Test K2 Rename':

SP Deployment Error



Presently this issue is only found when using the SharePoint Package and Deployment tool. This tool is legacy and only available on blackpearl 4.7. Therefore the issue is not present on K2 Five or later where the Package and Deployment MMC is used.

To workaround this on 4.7, avoid renaming SharePoint lists. List templates can be used and create the list initially with the desired name to avoid errors.

0 replies

Be the first to reply!