• In general, if there is a missing reference error, check that there are no errors or incorrect mappings on the source, remap accordingly and repackage and deploy
• For Missing Reference workflow errors, the Workflow could be pointing to the wrong or missing SmartObjects, Views, and Forms

• If there is a missing reference error, check that there are no errors or incorrect mappings on the source
• Check if the workflow on the source is referencing the correct SmartObjects, forms, and views. Remap if required, package and deploy again on target
• Check if the artifacts to be deployed are part of a SharePoint solution (even if only in the form or subform references). In the case where artifacts to be deployed are part of a SharePoint solution, all the SharePoint solution SmartObjects must be included in the package to add the required references. Depending on the scenario, you do not necessarily need to deploy all the SmartObject artifacts included in the package to the target environment, but including all the referenced artifacts will help to mitigate the missing reference error. 

This most likely is the result of having manually removed either the list or library SmartObject, service object, or workflow related items when the package was created.

• Check the source and target environment SharePoint List or Libraries to make sure no columns or fields were removed. If so, add them back. The SharePoint Lists or Libraries in the package must match the target and source environments SharePoint Lists or Libraries.
  Some columns in SharePoint Lists or Libraries are hidden by default. Check the List or Libraries and make sure hidden columns match on the source and target SharePoint List or Libraries before packaging and deploying.
• If your SmartObjects are affected, check that the system name is correct for those SmartObjects and point them to the right SharePoint site URL
• Check if the artifacts to be deployed are part of a SharePoint solution (even if only in the form or subform references). In the case where artifacts to be deployed are part of a SharePoint solution, all the SharePoint solution SmartObjects must be included in the package to add the required references. Depending on the scenario, you do not necessarily need to deploy all the SmartObject artifacts included in the package to the target environment, but including all the referenced artifacts will help to mitigate the error. 

• This can happen when creating service objects and their associated service instances and SmartObjects using the SmartObject tester tool
• For K2 Cloud Package and Deployment objects based on O365 (SharePoint) SmartObjects, Package and Deployment may not have had a Microsoft Online AppOnly token to access SharePoint Online
• The field may exist in the source environment but not on the target environment. The field may also only be present on new SharePoint Document libraries and may not in older libraries
• The field may have existed on the SharePoint Document library but no longer does, which can cause the error

• A possible troubleshooting solution is to restart the K2 Service
• The issue can be caused when the user running Package and Deployment has not been issued with a Microsoft Online AppOnly Token to access SharePoint Online.
• To generate a Token, please use the following steps:
  1. Open SmartObject Tester Tool as the same user account attempting to create the Package.
     The SmartObject tester Tool is only available on K2 Five or earlier and K2 Platform Classic
  2. Execute any of the SharePoint Online list/library related SmartObjects.
  3. A prompt should display stating: Please retry the operation after successful OAuth Authorization.
  4. A browser window will display for Microsoft Online Login.
  5. After signing in, an “Authorization Successful” message will display.
  Alternatively use the following steps:
  1. Open SmartObject Tester Tool as the same user account attempting to create the Package.
  2. Create a new SQL Server Service Instance.
  3. For Authentication Mode, Select OAuth.
  4. For OAuth Resource, select the MSOA – [GUID].
  5. For “Database – Required”, enter any text. Click Next
  6. A prompt should display stating: Redirecting for Authorization. Retry after successful authorization.
  7. A browser window will display for Microsoft Online Login.
  8. After signing in, an “Authorization Successful” message will display.
  9. The Add Service Instance can be canceled at this point.
  10. These steps would have created the required AppOnly Token and Package and Deployment will be able to successfully package the SharePoint Online SmartObject.
• Ensure the source and target SharePoint Document libraries are in sync
• Refresh and regenerate the SmartObjects on the SharePoint Artifacts page. Make a backup of the SmartObjects before applying this resolution 

1. Locate the SharePoint list(s) associated with the error.
2. Go to the K2 settings page for the list.
3. Delete all existing SmartObjects.
4. Regenerate the SmartObjects using the K2 list settings page.
5. Create the package.  The original error is gone, but any views/forms that reference the original SmartObjects show an error in P&D.  "Form [name] is referencing SmartObject Property [name] on SmartObject Unknown."
6. Use the designer to edit each affected view and form.  No error badges will appear.
7. View each rule shown in the P&D error details.
8. Simply viewing the rules reconnects them with the right SmartObject name.
9. Save the form/view and check-in each item.
10. You should now be able to create the P&D package.

• Deploying a package to a target environment which has a different K2 version or Fix Pack from the source environment can cause the 'Method could not be resolved' error
• The Package and Deployment tool could be out of sync with the server where the package is being deployed to

• Ensure that the source and target environments are on the same K2 version or Fix Pack
•  Ensure that you have updated Client Machines where the Package and Deployment / Client tools are installed.
• If you are using K2 Cloud, obtain the latest version of the P&D tool - see KB002316 for instructions.

• The issue can occur due to a mismatch in the SharePoint Library settings between the source and target machines
• Using ShareGate to duplicate SharePoint lists from classic to modern templates can cause the issue to occur

• Enable the Major Version setting on the Library, re-create the package and deploy to the target environment
• Make sure the target library matches the source library, re-create the package and deploy to the target environment

• Use K2 Management site to assign the publishing user Publish rights on the SmartObject/s in the package. 
• Use K2 Management site to manage SmartObject Security on the SmartObject. 

• Don’t include non SharePoint related items in a package with SharePoint artifacts.
• Include the same SharePoint SmartObjects and don’t include them By Reference. They need to be included in the package. All the other forms and views can be packaged By Reference, but the SharePoint SmartObjects must be packaged. When they are included you see the mapping screen during deployment and the tool refactors the GUIDs and then the system name and GUIDs of the SmartObjects will match and not be in conflict.

To resolve this error, follow the steps below:

1. Copy the K2HostServer.exe.config from "K2 blackpearlHost ServerBin" to "C:Temp". Create a Temp folder in C-drive beforehand
2. Rename the config file to web.config
3. Open a command prompt and change the directory to "C:WindowsMicrosoft.NETFrameworkv2.0.50727"
4. Run the following command:
   > aspnet_regiis -pdf "connectionStrings" C:Temp
5. Open the web.config in "C:Temp"
6. Locate the following strings under the connectionStrings section and change the password accordingly:

   <add name="HostServer" connectionString="Integrated=False;IsPrimaryLogin=True;Authenticate=True;EncryptedPassword=Fals 
   e;Host=BLACKPEARL;Port=5555;UserID=Admin;Password=k2pass;SecurityLabelName=K2SQL;AuthData=1" />

   <add name="WorkflowServer" connectionString="Integrated=False;IsPrimaryLogin=True;Authenticate=True;EncryptedPassword=Fals 
   e;Host=BLACKPEARL;Port=5555;UserID=Admin;Password=k2pass;SecurityLabelName=K2SQL;AuthData=1" />

    

7. Save the file
8. Rename web.config to K2HostServer.exe.config and replace the current config file in "K2 blackpearlHost ServerBin"
9. Restart the K2 Service