Deprecation of the Physical Data Model

The motivation for these changes is to simplify modeling and model management. Originally, the physical data model (PDM) was defined on top of the data source, while the logical data model (LDM) was defined for each individual workspace. The new approach to using LDM unifies this process, consolidating both types of information within a specific workspace. The ability to work with both LDM and PDM entities in a single location also simplifies the use of SQL-based datasets.

New Way of Using LDM and PDM

The revisions are centered around user interaction with the LDM and PDM via the REST API. This is transparent to the front-end, meaning that user experience within the browser-based application remains unchanged.

When your workspaces transition to this new functionality, their LDM will be enhanced to include supplementary PDM details, such as column data types (for attributes, labels, facts, and references), table paths (for data source tables), and workspace data filters.

From now on you should transition all your LDM backups and custom processing related to LDM or PDM to the new format, and cease using the PDM along with the deprecated API endpoints (further details are provided in the next section).

Deprecated API Endpoints

Several REST API endpoints, along with PDM-related OpenAPI sections, have been deprecated. If you are currently using them, you’ll need to transition to the new endpoints within the deprecation period specified below.

The deprecated endpoints and their associated schemas are as follows:

  • GET and PUT on:
    • /api/v1/layout/dataSources/{dataSourceId}/physicalModel endpoint
    • and related DeclarativePdm schema
  • DeclarativeTables schema in GET and PUT on:
    • /api/v1/layout/dataSources and
    • /api/v1/layout/organization endpoints

Deprecation Period

The deprecated API endpoints will remain available until November 2023. Starting December 2023, these endpoints will no longer be accessible in GoodData Cloud.

Modeler changes

There haven’t been significant alterations in terms of the modeler’s functionality. With the removal of PDM, having DataSource.USE and Workspace.ANALYZE permissions will now suffice to work on and edit the model.

Column data types are now housed within the logical model. A new dropdown menu has been introduced to modify these directly (whereas before they were set to read-only). Additionally, these types will be automatically updated when the “data source refresh” button — located to the right of the data source dropdown — is clicked.