Is there a registry setting, .config file setting, database setting, etc. that P&D looks at while deploying to a K2 Five environment (on-prem) to check for version numbers? We have bits that we know 100% will work in a K2 Five environment, but we are unable to deploy because the package was built from a K2 4.7 farm. We would like to temporarily suppress the error that is preventing P&D from deploying to the package in our K2 Five farm.
Page 1 / 1
Hi erice,
I am afraid packages created on version 4.7 and prior cannot be deployed to K2 Five. Please see more details in the article below.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.