1. Null Column Values Causing Hidden Records in the UI

Description
A database issue was identified where null values in critical columns caused related records to disappear from the user interface. The following elements were affected:

• Keys

• Cylinders

• Locking Systems

Although the data existed in the database, it did not appear in the UI, resulting in inconsistent system behavior.

Impact

• Users could not view or manage affected entries.

• Locking systems appeared incomplete or missing.

• Data exports and overviews did not match the actual database contents.

Resolution

• Implemented improved validation to ensure UI visibility no longer depends on null-sensitive fields.

• Added safeguards to prevent incomplete records from causing display failures.

• Updated internal logic to handle missing values more reliably.

2. Empty Tile Structures Inserted During User Role Assignment

Description
During role assignment, the system occasionally inserted empty tile structure values into the database.

Root Cause
A misconstructed LIKE operator in the query prevented the correct tile structure from being retrieved. This resulted in incomplete permission data being written.

Impact

• Incorrect or missing UI tiles for affected users.

• Permissions did not reflect the assigned roles.

• Administrators needed to manually correct user configurations.

Resolution

• Corrected the query logic responsible for retrieving tile structure information.

• Fixed and validated the LIKE operator to ensure proper pattern matching.

• Added protective checks to prevent saving empty tile structure entries.

3. Unauthorized (401) Error During License Registration

Description
When attempting to activate a license online, the system displayed an Unauthorized (401) error.

Root Cause

• The issue was not caused by Chargebee authentication.

• The application failed to correctly load its configuration settings, causing it to miss the Chargebee API key during activation.

Impact

• Online license activation failed.

• Users were required to retry or switch to manual activation.

Resolution

• Corrected the settings-loading process to ensure the Chargebee API key is consistently available.

• Added validation logic to confirm that required configuration values are present before starting the activation process.

• Improved error handling to prevent false 401 errors when configuration data is incomplete.