Good day,

Indeed, it is not possible for packages created in K2 4.7 to be re-deployed in K2 5 especially K2 5.2 this is because most features that came with K2 4.7 black pearl are no longer supported in K2 5.2. Therefore, when you try to deploy packages made in K2 4.7 to K2 5.2 it will deploy though you will have to upgrade your package to the current version that you are using.

Legacy features are made to make sure that your package is deployed on your current environment and the package can be upgraded to the current version that you are running K2.

The legacy design features also come when your installation of the K2 five is an upgrade and not a fresh new installation.

Please browse the following links for more clarity.

1. https://help.k2.com/onlinehelp/k2five/userguide/5.0/default.htm#LegacyDesigntools/Cross_Designer_Compatibility.htm
2. https://help.k2.com/onlinehelp/k2five/userguide/5.0/default.htm#PackageAndDeploy/PandD-Considerations.htm%3FTocPath%3DCreate%7CDeploying%2520K2%2520applications%7C_____4

Given you feel that the response is of use or a solution to the issue posted, please mark it as “Mark as solution”, “Kudo” or both options.

"K2 will not accept any liability for any issues arising from actions taken in respect of the information provided by any forum member.”

Kind regards,

Dumisani

Hi K2 Developer

What you need to know when upgrading

• You can upgrade to K2 Five (5.2) from both K2 4.7 and K2 Five (5.0 or 5.1).
• You cannot upgrade directly from K2 4.7 to K2 5.2 if you have 4.7 installed on-premises with the K2 database in Azure SQL. In this case, you must first upgrade your K2 4.7 installation to K2 Five (5.0), then upgrade to K2 Five (5.1) and then to K2 Five (5.2).
• The delete option in SmartObject Security (K2 Management>Integration>SmartObject Security) has been deprecated, for more information on the expected upgrade behavior change and manual configuration see KB0002667.
• In this release access to the K2 Designer site is solely controlled by configuring rights using the Designer node in K2 Management. For more information on the change in behavior see KB002722 - K2 Designer rights changes in behavior.
• Refer to KB002384 - Known issue: Value cannot be null Error Upgrading to K2 Five (5.1) before upgrading, if affected you must run a script to fix the error before continuing with the upgrade.
• The K2 installer now blocks installations if your SQL Azure databases do not meet the minimum requirement. See the Compatibility and Support Matrix for the minimum supported version.
• If you are upgrading from K2 4.7, read KB002045 for all the information on install changes, considerations, changes in the product, and how these affect your current environment.
• Before upgrading to K2 Five (5.2) ensure all App artifacts in the category All Items/Apps/K2/Framework/Coreincluding all child categories of the Core category are checked in. Failure to do so will result in a failed upgrade. See KB002419 for the resolution if you have already upgraded before checking in the artifacts.
• If you are using K2 for SharePoint and upgrading from K2 4.7 there is an updated app available. You must upgrade the K2 for SharePoint app and re-run the K2 for SharePoint registration wizard.
• If you are upgrading from K2 Five (5.0 or 5.1) and use the K2 for SharePoint app, do not run App Deployment only rerun the registration wizard after the upgrade.
• As of K2 5.1, SharePoint Application Accelerators are no longer available. Existing applications based on SharePoint Application Accelerators continue to function, but the ability to deploy new applications based on these Accelerators has been removed and replaced with K2 Apps.
• In K2 Five you had the ability to grant people API administrator rights allowing them to administer Workflow REST and OData APIs. The rights were configured in the API Administrators section in K2 Management> Integration> API Configuration. In K2 Five (5.1) the API Administrators rights are part of the Server Administrator and can no longer be separately configured. The API Administrators section in the K2 Management> Integration> API Configuration node is removed.
• If you upgraded to K2 Five from K2 4.7 and had the Sort By SmartBox setting enabled in the Legacy Design tools, after upgrading to K2 Five (5.2) the selection will be disabled in the database and you need to manually enable the new SmartObject property index setting on the SmartObject.

I hope this answers your question, should you find the above information useful to your problem please Mark as "Accepted Solution and/ Kudo"

Thank you.

K2 will not accept any liability for any issues arising from actions taken in respect of the information provided by any forum member