Hi Vishal,

When you working with K2 integration with SharePoint 2013, creating and deploying K2 artefacts dependent on SharePoint items, you should always be aware of what supported and what not suppported, say for instance if you are running on K2 for SharePoint 1.0.1 which is not supporting with building K2 artefacts for SharePoint lists having lookup columns, in this case you can create a packge, creating a packe will not have a problem, but when it comes to deploying the package to another environment you will have issues, thus i would suggest you to take a lokk at the below cheks before you go ahead with K2 for SharePoint artefacts deplyment;

1) What version of K2 are running? depending on that please go through what supported and not suppoted wiith K2 for SharePoint. Follow the below link

http://help.k2.com/onlinehelp/K2ForSharePoint/UserGuide/1.0.1/default.htm#About_K2_for_SharePoint/CompatibilitySecurityPermissionsandConsiderations/Supported_and_Unsupported_Artifacts.htm?Highlight=unsupported

2) Make sure the SharePoint artefacts are pre available on the deploying environment which are simlar to environment from where you have built the package.

Hope the above checks would help you!

Cheers,

Prajwal Shambhu

Building on what Prajwal in his second point. Here is also a list of Sharepoint artifacts and data values that you should make sure are set in the cloned environment before deploying your K2 package.

• SharePoint container artifacts like Lists/Libraries/Groups/Sites
• SharePoint content artifacts like List Items/Documents/Permissions
• SmartObject Data
• Reporting Data

http://help.k2.com/onlinehelp/K2ForSharePoint/UserGuide/current/default.htm#Working_with_K2_for_SharePoint/Deploy.htm

Here is another useful piece of documentation that may help you.

Deploying Application Elements to a new Sharepoint Environment:

http://help.k2.com/onlinehelp/K2ForSharePoint/UserGuide/current/default.htm#Deploy/DeployAppElementsDifferent_SPEnv.htm

Evan