Skip to content

Version 26.10.2.0

What's new

Measure health cards

Every measure in the RMD now has a health card that shows whether the measure is ready to be used in fact tables and data marts, so problems can be found and fixed before they lead to wrong numbers in reports. The card brings together the results of five automatic checks. "Name verification" checks that the name is at least two characters long and is not used by another measure, dimension or fact. "Formula verification" looks for errors in the formula, circular dependencies, and dependencies with errors at any level of the lineage. "SQL generation" confirms that SQL can be generated for the measure. "Potential duplicates" finds other measures calculated with the same formula, even under a different name. "Incomplete description" lists the RMD columns describing the measure that are not filled in. Formula verification and SQL generation run only for measures with the "Active" status. Each check, and the measure as a whole, gets one of five statuses: "OK" (green), "Error" (red), "Attention" (orange), "Undefined" (a question mark: the check has not run yet or could not be completed) and "Disabled" (a pause icon: the check does not apply to the measure). The checks run again in the background after the RMD is edited or imported from a file and after a version is imported from Git, when the "Details from RMD" window is closed after a measure was saved, and for all measures of all projects every day at 19:00 UTC by default; they can also be rerun manually at any time. The overall status is shown as an icon next to the measure name in the RMD, in the "Details from RMD" window, in the formula builder, lineage, impact analysis, the data model, fact tables and data marts, and hovering over the icon shows a tooltip with the problems and warnings found. The "View health card" button on the toolbar of the "Measures" tab and in the "Details from RMD" window opens the "Measure health card" dialog. It lists every check with the time and result of its last run and the details of what was found; clicking a matching RMD element opens its "Details from RMD" window. From the dialog you can rerun a single check or all of them and open the measure for editing. Viewing cards and rerunning checks are available to every role. A measure with the "Error" status cannot be added to a fact table or a data mart, while measures that are already there stay and can be removed; the view of a data mart that contains such a measure cannot be created or updated until the problem is fixed. Along with the new checks, the measure description, display data type, measure type, formula and status became required RMD columns, as did the descriptions of dimensions and facts, whereas "Verification report" and "Comment" are no longer required; required columns can no longer be hidden. The "In progress" status no longer carries special restrictions: like an empty or a custom status, it is not treated as an error anywhere in the product, and only the "Archived" status is.

Improvements and bug fixes

  • The "Details from RMD" window now has a "View change history" button that opens the change history of the element, the same as the corresponding button in the RMD (IMP-3329)
  • A formula that refers to an element that does not exist yet now picks it up as soon as an element with that name is created or an existing element is renamed, so lineage and verification show the link without saving the formula again; this works for measures, derived dimensions and derived facts, and names with brackets such as "Revenue (net)" are matched as well (IMP-3150)
  • Only developers, company administrators and superadministrators can change the settings of RMD columns: analysts and viewers can no longer edit columns in the column settings window (IMP-3271)
  • Data mart and connection names are now checked as they are typed: the broken rule is shown under the field and the "Save" button stays disabled, and if a name is still rejected, the reason is always shown; data source names must now be unique regardless of letter case, and a taken name is reported under the field (IMP-3187)
  • In on-premises installations, creating, updating, refreshing or deleting a data mart view is no longer lost when the user signs out or the application server restarts: the operation can run as long as the database needs, its outcome is kept as a personal notification shown at the next sign-in, and an operation in progress can be stopped with "Cancel update" (IMP-3218)
  • When the transfer of access rights is enabled, a data mart table on PostgreSQL or ClickHouse now receives the row-level security policies of all its protected sources, instead of denying access to the restricted users whenever more than one source has such policies (IMP-3267)
  • When the transfer of access rights is enabled, a data mart table on Microsoft SQL Server now receives the row-level security of its sources, so it is no longer denied to every reader (IMP-3268)
  • Many users can now verify measures and preview data marts at the same time: connections to the target database are released after every query instead of piling up, and a failed connection is reported with its actual cause instead of an unknown error (IMP-3221)
  • Users are no longer signed out at random under heavy load when the product's database responds slowly or fails for a moment (IMP-3220)
  • The session is no longer ended when the check of the user's IP address could not be completed, for example because of a network interruption; the user is signed out only when the address is actually not allowed (IMP-3239)
  • A data source can now be deleted after the projects that held connections to it have been deleted, and the connection count of a data source no longer includes connections of deleted projects (IMP-3188, IMP-3223)
  • In on-premises installations, dates and times such as the event time in the audit log and the update date of a data mart view are now shown correctly instead of being shifted by the time zone offset (IMP-3190)
  • Fact tables and data marts created by importing a project version from Git or from an archive, including through the API, are now owned by the user who ran the import, as if they had been created by hand (IMP-3206)
  • The public API v2 now accepts formulas with NULL, IS NULL, IN, BETWEEN and a unary minus, which the formula editor already supports, and a dimension can now be added through the API to a dimension group created in the interface (IMP-3214)
  • Users can no longer see data of companies and projects they have no access to, such as database connections, companies and their users, or the data marts and RMD of other projects, and this information is available only to signed-in users (IMP-3168)
  • The details of a database connection are available only within the project the connection belongs to, and the user name and password of the connection are no longer sent to the browser (IMP-3219)
  • Cloning a data mart no longer exposes confidential details of the user's account (IMP-3234)
  • A superadministrator now sees and uses only the data sources, Git connections and identity providers of their own company, so a project can no longer be exported to or imported from another company's Git repository (IMP-3228)
  • When the access of a project manager to a project is lowered to analyst or viewer, or revoked, the change now applies to everything they do, not only to the interface, and cloning a project now requires access to it (IMP-3272)
  • Only a superadministrator can rename a company: the restriction now applies everywhere, not only on the "My company" screen, and the company name in the user profile is read-only (IMP-3255)
  • A company administrator can no longer view, change or delete companies they do not belong to, and only a superadministrator can delete a company (IMP-3261)
  • The base company created at installation can no longer be deleted: its delete action in the companies list is disabled, with a tooltip explaining why (IMP-3262)
  • A company name is now checked by the same rules on renaming as on creation, and the message names the rule that was broken (IMP-3256)
  • Renaming a company to a name that is already taken, in any letter case, now shows a clear message instead of an internal error code (IMP-3263)
  • Inviting a user with a role that does not exist is now rejected with a message about the role rather than one about an existing email address, and a superadministrator can no longer be invited when a company is created (IMP-3264)
  • The "My company" page opens only for superadministrators and company administrators; other users are redirected to the project list, even when they type the page address, and only these two roles see the actions for editing and removing company users (IMP-3257)
  • Choosing a file that is not a valid license on the "My company" screen now shows an error notification instead of nothing at all (IMP-3259)
  • Sorting companies by the "License end date" column now works correctly (IMP-2717)
  • In on-premises installations, sending data to Yandex Metrika can be switched off with the YANDEX_METRIKA_ENABLED setting in the installation's .env file; the change takes effect when the product containers are recreated or a new version is installed (IMP-3338)
  • Typos, untranslated texts and wording errors were fixed in the interface and in server messages (IMP-3327)