"Value Cannot be NULL. Parameter name: key" error displayed against custom SmartObjects with hardcoded input properties post 5.1

  • 16 February 2021
  • 0 replies
  • 206 views

Userlevel 5
Badge +20
 

"Value Cannot be NULL. Parameter name: key" error displayed against custom SmartObjects with hardcoded input properties post 5.1

kbt147289

PRODUCT
K2 Five 5.1
BASED ON
K2 Five 5.1
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

This issue appears with custom SmartObjects that were built with input properties hardcoded. When executing methods post 5.1 upgrade, 'Value Cannot be NULL. Parameter name: key' error is displayed.

Symptoms

'Value Cannot be NULL. Parameter name: key' error is displayed when criteria in regards to custom SmartObjects having their input properties hardcoded when built is met.

Resolution

This issue was resolved with Fixpack 3

0 replies

Be the first to reply!

Reply