Symptoms
After selecting a Site Collection from the drop-down, receive the following error when using the Create List Item wizard in a workflow:
Error Message: SmartObject Server Exception: Inconsistency detected between SmartObject 'xxxxx' and Service Object 'yyyyy' during loading of SmartObject Definition. Service Object : 'yyyyy' not found in Service Instance 'andltsitenameandgt.sharepoint.com - sites - andltsite collectionandgt' Definition.
Diagnoses
When selecting a Site Collection for use in the Create List Item wizard, K2 performs a consistency check on all SmartObjects that live in that Site Collection. If an inconsistency is detected between any SmartObject and the associated Service Object an error will be thrown.
Resolution
This issue was initially caused when a manual refresh of the SharePoint 2013 Service Instance was done on the Appit instance from the K2 Management page, instead of the recommended method (running the Registration Wizard). Refreshing the service instance in this way only describes the SmartObjects, and none of the associations required for the solution to function correctly. This causes Service Objects and Smart Objects to become "out of sync", throwing errors whenever the user attempted to use the "Create List Item" wizard in a workflow, as K2 does a consistency check during the selection of a Site Collection, to verify the integrity of all SmartObjects on the Site.
The way to fix this is to go to each List/Library that has been Appified and regenerate the SmartObjects.
However, before the cause and solution of this issue were identified, several Lists/Libraries and their associated artifacts were deleted by the end users, making it impossible to regenerate those SmartObject. This necessitated intervention from K2 Appit Support Operations, as they had to RDP into the K2 Server and use the SmartObject Tester Utility to manually delete the out-of-sync SmartObjects.
Once all of the out-of-sync SmOs were deleted, the Create List Item wizard was able to function correctly.
In addition, a patch was applied to all Appit environments so that doing a manual refresh of the Service Instance will function the same as refreshing it from the Registration Wizard, so this should not happen again.
