Release note - beVault 3.10.1

List of changes

metaVault

• API Keys: Fixed an issue where the newly generated secret key was not visible after duplicating an existing API key, making it impossible to use the new key.

• Data Package: Prevented the creation of two hub mappings with the same business key within a data package table. This duplication caused errors in other parts of the application (e.g., when filtering model columns for an Information Mart script).

• PIT Tables: Fixed an issue where a PIT table could not be deleted if the entity had an active data quality control, even when the DQ check was not linked to the same snapshot. Deletion is now only blocked when the DQ control targets the same entity and the same snapshot.

• Staging Tables: Fixed an incorrect error being sent to logs when removing a column used in a mapping from a SQL-view-based staging table. The application now returns a clear, user-facing error: "Cannot remove column [col name] because it is used in a mapping."

• Staging Tables: When saving staging table SQL code that contains errors, beVault now returns the actual database error message instead of a generic HTTP 500 error, consistent with behaviour at deployment time.

• IBM DB2 – Effectivity Satellites: Added a Query Option parameter to select between a MERGE query and an INSERT/UPDATE approach for effectivity satellite loading. A global option is also available to manage this preference across the project (see Metavault Configuration | Servers).

• Async Stability: Removed all instances of Task.Result and Task.Wait() throughout the application to properly leverage async/await, eliminating potential deadlocks and async scheduler bypasses.

• Load Queries per Environment: Loading queries are now split by environment when deploying a new version. Each environment gets its own dedicated folder for its load queries, preventing conflicts when working on projects that target multiple database types with different TRUNCATE handling strategies.

• Environments: The "is production" flag on an environment no longer restricts editing of deployed entities. It is now purely informational.

States

• Orchestrator (States): Fixed an issue where the close button (×) disappeared after editing and saving a state machine, preventing the user from closing the tab.

Api

• Data Package List: Added the missing dfakto REST pagination mechanism on the data package list endpoint.

• Information Mart Scripts Ordering: IM Scripts retrieved via the API are now sorted by Order then by Name by default.