Dataland v97.0: Release notes - d-fine/Dataland GitHub Wiki

We updated our Component Library PrimeVue from version 3 to version 4. This introduced a change in our frontend styling, but the functionality of the Dataland webpage should have stayed the same more or less.

Previously, columns were inconsistently ordered. E.g., if entries had missing values, subsequent entries with complete data would have incorrectly positioned columns. Therefore we fixed inconsistent column ordering in portfolio and company exports when components have multiple properties (e.g., currency fields with value and currency columns) by adding ordered schemas to the specification service. For this a new endpoint was introduced: GET/{frameworkSpecificationId}/resolved-schema, which returns the complete schema with all component structures resolved to their primitive types, including the correct column ordering for multi-property components like currencies. Additionally the export service was updated in order to make use of the schema definitions for the correct export:

Therefore data exports now have consistent logical column orderings regardless of data completeness in individual entries.

In Community Manager, there is a new controller, User Validation Controller, which currently has exactly one endpoint: POST /user-validation/email; see the first screenshot. The endpoint accepts an email address in the form of a one-field request body, and on success, it returns basic information on the Dataland user registered under that email address, namely their Dataland user ID, first and last name together with the passed email address; see the second screenshot. Only Dataland admins and users who are owner or member admin of at least one company on Dataland can use this endpoint.

The GET /company-role-assignments endpoint of our Community Manager, which allows for a filtered search for company role assignments, has been modified to return so-called extended company role assignments; see the first screenshot. In addition to the usual information from a company role assignment (namely, Dataland company ID, Dataland user ID and role of the user in the company), these also contain the first and last name as well as the email address of the user; see the second screenshot.