Hi   @ruchiaga

Have you perhaps installed any patches into your environment and are you experiencing the errors in PnD but not during designer? if so please read and follow below.  

Probably this error is referencing a view/form property on a SmartObject that could not be found.

Please try to update the XML for the rule because it might be still referencing a renamed or deleted SmartObject.  

Once this is done go through the view and form rules for the view/form to check if there aren't referencing renamed or deleted Smart objects, and then go back to P&D and shut it down and reopen the P&D tool to clear any cached data. 

Than reanalyze your package again.

These issues are normally related to design changes that leave orphaned rules or fields. However, the missing ALM badges for dependency issues can also be related to the upgrade from 4.6.11 to 4.7.

This is because we increased our ability to search the code and find possible issues before the solution is packaged and deployed.

Kindly feel free to mark as “Accepted solution, kudo and/me too” if you find this information answered your question or leads to your answer.

Thank you and kind regards,

Dumisani

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

Hi ruchiaga,

To further assist you  I recommend reviewing the documentation and then examine your Forms/Views for dependency concerns. The Package and Deployment tool can be used to point you toward the Froms/Views that have the issue. When you go to Package the forms, K2 checks all the Forms for these badges and will tell you the location of each Form/View that needs to be changed.

Here is the link to our K2 4.7 SmartForms documentation on dependency checking:

http://help.k2.com/onlinehelp/k2smartforms/userguide/current/default.htm#Create/Fixing_Dependency_Issues.htm?

Please let me know if you have any questions or if you need any assistance.

Kindly feel free to mark as “Accepted solution, kudo and/me too” if you find this information answered your question or leads to your answer.

Thank you and kind regards,

Dumisani

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

Hi  @ruchiaga;

There's depandance dialog box usually handle the kind of situation:-attached---preffebly remove all manually

Automatically removes all dependencies of the item deleted. When selecting this option on a Form, only Form-level dependencies are removed. In certain instances, dependencies cannot be removed. (For example, if a concatenate function requires at least one value and this value is deleted, the expression can't evaluate so the dependency is not removed. The dependency is flagged with an indicator if it cannot be removed so that you can fix it manually.)
You may find it useful to start at the lowest level (such as a View) to remove all dependencies on the View and work your way up to Form level.

regards;

widson

Hi Ruchiaga

See the following Kb article, is related to the problem you are facing .

https://help.k2.com/kbs100121

Should you find the information from the article useful or leading you to the answer please mark as "Solution and/or Kudo", as it will assist other k2 developers with relevant information in the near future.

Best Regards

Elvis

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