Release Notes v5.44

What's new?

• Ursa Reference object type, which loads Ursa-curated reference data sets into the environment. These objects will typically be managed by Ursa Health, because they must link with Ursa Health Standard Reference files, which are kept in an Ursa-owned storage container.
• Foreign keys can be designated in the Object Metadata panel for fields with a field group of Data Model Keys. These keys are strictly informational and are not enforced in the database.

What improvements have we made to existing features?

• Lookup table keys now support wildcards and ranges. The behavior of wildcard and range lookup table keys mimics the behavior of wildcard and range value set values. As with value set values, users can denote a lookup table key that has a star or a dash that should be interpreted literally (and not as a part of a wildcard or a range) using the "Is Literal Value" checkbox in the lookup table setup screen.
• "Prevent Passive ELT" option for reports, which will keep the report from being included via the "Run affected reports" checkbox in the ELT screen.
• The following fields will not be overwritten during module import: "Prevent Passive ELT" (in objects and reports), "Is Locked" (in objects, measures, and models), and the contents of the "Incremental Load" and "Object Backup" panels in objects.

What's been fixed?

• Fixed a bug that had been introduced in 5.38.0 in which count measures when viewed in a results-over-time chart with a numerator filter or split applied would show incorrect results when served out of the optimized dimensional table.