< class="prominent-subhead ">

Unable to Package Salesforce Service Instance

~~repeating-content.html~~
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.
LEGACY/ARCHIVED CONTENT
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.

Issue

When you try to package up a solution that includes SmartObjects that depend on a Salesforce Service Instance, that instance does not appear as an option and it's not dynamically included in the package.

Symptoms

It doesn't need to add Salesforce Service Instance when creating a package using MMC, but SalesForce Service Instance should exist on the target environment.

Troubleshooting Steps

1. Create a package without SalesForce service instance.
2. You will need to have a SalesForce ready target environment. If not, manually add SalesForce Service Instance and generate SmartObject/SmartObjects.
3. Deploy the package to the target environment, which will give missing reference errors.
4. Next you will need to click on the missing reference SmartObject and configure.
5. Select Use Existing SmartObject from the Action drop-down and select the path for the SmartObject created on the target environment.