Unable to edit Views - Designer Hangs

  • 16 February 2021
  • 0 replies
  • 5 views

Userlevel 5
Badge +20
 

Unable to edit Views - Designer Hangs

kbt132468

PRODUCT
K2 smartforms 4.7
BASED ON
K2 smartforms 4.7
TAGS
SmartForms
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.
LEGACY/ARCHIVED CONTENT
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.

Issue

When Editing a view/form, a "SmartObject [xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx] could not be found" error is received.

 

After clicking OK on this error box the Designer will display the spinning wheel icon and hang straight thereafter.

 

The only way to exit is to close or reload the browser window.

Symptoms

K2 Designer hangs when attempting to edit a view or form.

Resolution

A specially designed script was used to detect the view connected to the SmartObject in question based on the provided GUID in the displayed error. This script is used to then determine if it would be safe to create a new SmartObject which can be used to point to the broken SmartObjects GUID, it will also be used to rebind the view and all references to point to the correct SmartObject which in this case will then be the newly created one. After doing this the view will then be editable without any problems although a clean up would also need to take place to clear the database of any and all orphaned items as well as references based on the old SmartObejcts GUID. The script is also designed to do this.

 

 

This will be a customer specific script therefore a series of scripts will have to be run on your environment to detect the missing GUID, its locations, where it is used, if it safe to preform this change and a clean up of the old references.

To get this script please log a K2 support ticket in which a support engineer will be able to assit in providing and applying the script to the environment in question.

 

Please note that direct database changes will place you in an unsupported state, log a support ticket for a K2 support engineer to assist. 

 


0 replies

Be the first to reply!

Reply