Katalyst: Operation Parameters missing or not accepting Decimal Values

In the Katalyst web application, operation dialogs such as Maintain Temperature may not display Time, Value, or Range parameters, or may fail to accept decimal values correctly.

While locale settings and backend compatibility can affect decimal handling, the most common cause is a version mismatch between the deployed SDBES/Application Server version and the imported KAT_Operations record set. When Operations records are imported from a different SDBES version, parameter metadata may become incompatible, causing fields to be missing or behave incorrectly.

1. Verify the installed SDBES/Application Server version.
2. Confirm that the KAT_Operations record set was exported from the same version.
3. If the versions do not match, export the Operations records from a matching environment and import them into the target system.
4. Verify that required backend components and endpoints are supported by the installed version.
5. Confirm that the application and service machines use the appropriate locale settings (for example, en-US) if decimal values are required.
6. Restart relevant services and clear application caches, if applicable.
7. Open an operation such as Maintain Temperature and verify that the Time, Value, and Range fields:
   • Appear correctly
   • Are editable
   • Accept and save decimal values properly

Note: Locale settings may affect decimal parsing but will not resolve missing parameter fields caused by a version mismatch in the KAT_Operations record set.

Root Cause

The KAT_Operations record set was imported from a different SDBES version than the one deployed in the environment, resulting in incompatible operation parameter metadata. Importing a version-matched record set resolves the issue.