Troubleshooting Blank K2 Forms After a K2 Upgrade

Ever performed a routine K2 Upgrade with no error only to find your forms and views have pulled a vanishing act? It’s a frustrating scenario: everything looks perfect in K2 Designer, but at runtime, you're greeted with discouraging blank screen.

If you’re staring at a white page where a business process used to be, don't panic. You likely aren't looking at a broken installation, but rather the result of a bug fix working exactly as intended.

The Cause: When a Bug Becomes a Feature

In older versions of K2, a specific bug allowed forms and views to remain visible during runtime even if their Visibility property was explicitly set to "False".

Because the setting didn't actually hide anything, many developers inadvertently unchecked the "Visible" box or left it disabled without realizing it. Once you upgrade to a version with this fix, K2 "corrects" this behavior. The system begins honoring that checkbox again, causing those forms to disappear from the end-user's view as instructed by the metadata.

The Quick Fix: K2 Designer

If you only have one or two problematic forms, the manual fix is straightforward:

  1. Open the affected Form or View in K2 Designer.

  2. Navigate to the General options tab.

  3. Locate the Visible property.

  4. Ensure the checkbox is selected.

  5. Save and Finish.

  6. Check it in.

Proactive Discovery: The SQL Shortcut

If you manage a large environment, checking every form manually is a chore. You can quickly audit your entire database to find hidden forms using the following SQL script. This query scans the Form XML properties to identify any items where IsVisible is set to false.

SQL
SELECT 
    [Name], 
    [DisplayName], 
    [Properties] 
FROM [Form].[Form] 
WHERE CAST(Properties AS VARCHAR(MAX)) LIKE '%IsVisible</Name>%<Value>false%' 
AND CreatedBy <> 'K2SQL:System'

Note: Perform the Visible property updates through the K2 Designer interface to maintain environment integrity.

Comments

Post a Comment

Popular posts from this blog

Blocking Error during K2 5.6 Server migration

  Error Encountered: Error during K2 5.6 migration to a new machine, keeping the SQL server unchanged. Error message:                       20:49:59:>> Certificates.FindCertificate: Found 1 certificates                       20:49:59:>> RegisterShard.Execute: Adding additonal connection string parameters to config service shard                       20:49:59:>> AdditionalConnectionStringParameters.AmendSQLConnectionString: Additional connection string parameter value: empty                       20:49:59:>> AdditionalConnectionStringParameters.AmendSQLConnectionString: Additional ConnectionString Parameters is empty                       20:50:04:>> AnalyzableAction.PopulateValidate...
Read more

Client Credentials flow with K2 Cloud with Odata, Workflow REST or SCIM

Image
This guide outlines the steps to using the Client Credentials Flow for accessing Nintex K2 Cloud's OData, Workflow REST, or SCIM APIs. Before you begin: Ensure your environment is eligible for Client Credentials Flow by contacting Nintex support ( https://customer.nintex.com/cases/Pages/default.aspx ). Have a SHA256 hash of the client secret of your choosing ready. Steps: Onboarding: Open a support ticket with Nintex requesting the onboarding of the Client Credentials Flow for your environment. Provide the SHA256 hash of your the client secret. https://help.nintex.com/en-US/k2cloud/userguide/current/Content/IdProviders/ClientCredentials.htm You can Generate the secret hash from a Client Secret value in a .NET console application. The onboarding team does not need the actual secret value, only the hash of it. Use the following steps and code example to generate the hash: Add the  IdentityModel  NuGet package. Add the  IdentityModel  library reference in the ...
Read more

Blocking error RegisterServiceInstanceObjects when upgrading to K2 5.6/5.7

K2 5.7 Upgrade Error: Blocking Issue with Orphaned Service Instances Error Message:             07:30:39:>> AuthorizationBase.RegisterServiceInstanceObjects: Current ServiceType and ServiceInstance details: ServiceType.Guid = GUIDValue1. ServiceInstance.Guid = GUIDValue2 . ServiceInstance.Name = ServiceInstanceName             07:30:39:>> ConnectionHelper.GetServerInstance: Create 'AuthorizationClient' instance using ConnectionContext             07:30:39:>> AuthorizationBase.RegisterObject: Validate Parent             07:30:39:>> AuthorizationBase.Execute: Logged Error: Failed: System.Exception: Item 'GUIDValue1' does not exist    at SourceCode.Install.Package.Actions.Authorization.AuthorizationBase.RegisterObject(String name, Guid id, Guid parentID, Guid classID, String className, Boolean inherit, Boolean propagate, IIdentityReferenc...
Read more