Symptoms

Cannot deploy packages with SharePoint 2013 Smart Objects.

 

Diagnoses

Logged ticket error: Cannot deploy packages with SharePoint 2013 Smart Objects/ServiceObjects. During call it was seen items actions were being put in a deploy state which is not expected behavior. When opening the package to deploy it should have automatically analyzed the package, which it did not do.

Second error pertained to multiple missing references user gets when trying to deploy another package using the PandD tool. Advised to resolve these issues, as done previously, you first map the missing service object. This cleans up the majority of the missing references. Then you will again point to the list view in the new environment.

Third error occurs when trying to build a package. ?Peer Review Request? Form is referencing the ?SignatureAuthority? property on the ?SignatureAuthority? SmartObject that could not be found. We tried clearing the cache within the PandD tool, we also dug through the views and forms to confirm items were in string format and configured correctly. Error will go away if Signature Authority property is removed, however it is required by the customer. We took a look at the properties as well as the SmartObject configuration whoever we have not been able to get to the root cause. We do have a copy of the package which is being reviewed further.

 

Resolution

Logged ticket error: We manually selected the analyze option, closed the PandD tool, and then opened up again this time the package analyzed correctly. ServiceObjects and SmartObjects where put in proper action state of creating new types. We then mapped the service instances and list item which allowed package to deploy.

Second error: Advised to resolve these issues, as done previously, you first map the missing service object. This cleans up the majority of the missing references. Then you will again point to the list view in the new environment.

Third error: Adding the same rules with the issues onto the form and dragging in those picker controls that caused the issue when you create the package, if the new rules do not get flagged with the error then the old rules is where the issue lies, and if so, you will likely need to just use the new rules and mapping.