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.
This occurs when using the Package and Deployment application to deploy a package taken from a source environment and deploying it to a target environment.
This results in "Inconsistent SmartObject" errors during deployment, even after the K2 installation was successful.
This issue could be caused if a Smart Box SmartObject was accidentally changed to an Advanced SmartObject and then edited. Ensure that you rebind your rules where necessary based on the newly added SmartObject properties, then make a package of the project and deploy it to the target environment.
This issue can be fixed by completing the following steps:
- Deploy the Production package (working package) onto the source environment. This will revert your SmartObject back to its default state where no additional properties are added and the SmartObject will be a Smart Box SmartObject instead of an Advanced SmartObject.
- You will then have to confirm that the properties for the SmartObject are the same in these four locations:
- From SQL
- From the Smart Box Service instance via the tester tool
- From K2 Designer
- From the SmartObject Explorer section in the tester tool
Now that you have confirmed that they are all the same you can add in your additional properties and they should automatically be reflected in all the locations specified above in step 2.