View Dependency Errors that are not being badged by designer.

  • 16 February 2021
  • 0 replies


View Dependency Errors that are not being badged by Designer

This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.


This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.


When trying to check in views an error is raised stating that the view has dependency issues although all badged items have been resolved.


You are not able to check in any views or forms as there are unresolved references that are not badged by the designer. When you have a data source control which was bound to a SmartObject. At some point this control was changed to a non-data source control pre 4.7 upgrade. This left lingering SmartObject properties on the control which was not cleaned. These properties cause the dependency on the SmartObject which no longer exists.




You should perform a change control on the offending control, and change it back to what the original control was. After doing this you will be able to check in the view and subsequently the form it was tied to as well.  To determine the offending control please log a k2 support ticket and reference this KB.

0 replies

Be the first to reply!