Project Metadata and Field Metadata blocks in Data Model Management

Here's a new feature that could significantly improve your model's performance by keeping you updated on the fields used in reports across your projects.

With this information, you can optimise individual project performance by removing unnecessary fields and refining your data sources to avoid extracting irrelevant information.

The Project Metadata block now includes a new fourth tab dedicated to this purpose.

To recap, the Project Metadata block consists of four tabs:

• Blocks: Lists workflow blocks used in the target project, including their names, types, and output JSON schema. 
• Reports: Lists report names and content tabs, along with the associated data source names. In complex workflows with multiple reports and data sources, this information becomes invaluable.
• Report Tabs: Lists report names and tabs, including internal and external URLs. This is helpful when distributing reports to different users, allowing you to control which tab a report opens on by using the tab URL.
• Report Fields: The NEW tab catalogues all fields used in each report, making it easier to manage.

By joining this data with the Field Metadata block, you can quickly identify unused fields in your model and remove them to enhance performance.

Note: These are fields in report data sources, not strictly fields from the input data. So, if you're working with a complex report data model that includes formulas, aggregates, or other transformations, you may see additional fields reported that aren't present in the input data.

Fields Metadata block will list the fields in this block's input, along with each field's metadata. This information can be joined with the Project metadata showing the subset of those fields, which are used in reports.