Guidelines - trillium_discovery - trillium_quality - 17.1

Trillium Beyond The Basics Guide

Product type
Product family
Trillium > Trillium Quality
Trillium > Trillium Discovery
Product name
Trillium Quality and Discovery
Trillium Beyond The Basics Guide
Topic type
How Do I
First publish date

Note the following when working with dynamic entities in the Control Center:

  • Dynamic entities cannot be used for Time Series Analysis because they do not contain the historical data needed to trend changes over time.

  • Dynamic entities used as input to Quality projects gives you added flexibility when the data source changes. You can for example:

    • Refresh data and run the project again

    • Run your project using a different sampling of data

    • Run your project pointing to another data source

  • If a data source file is deleted, its name modified, the directory where the linked files are stored is changed, or the Loader Connection data or directory for the source file is redefined, the drill-down to view the data rows will no longer be valid.

  • Since data must be fully loaded into an entity to evaluate attribute business rule compliance, Attribute Business Rules can only be evaluated in real entities. They cannot be evaluated in dynamic entities.

  • Since dynamic entities are linked to data source files, they are usually created much faster than real entities, especially when the source data is large (millions of rows). Conversely, because dynamic entity data is not loaded (and therefore not fully analyzed or indexed), filtering, running business rules, and drilling down on data takes longer than when working with a real entity.

  • Since there is limited analysis of metadata for dynamic entities, some drill-downs in the Summary Data View and from the attribute and entity right-click menus are unavailable. The following are unavailable:
    • Time Series Analysis
    • Discovery keys or dependencies
    • Create keys or dependencies
    • Re-analyze business rules
    • Analyze pending derived metadata
  • Use dynamic entities as a type of template, to store business rules in multiple entities grouped in a Baseline Analysis project, then run the rules against iterations of the same data. For example, each time the source data is updated (say, every week or month), copy the project, then load data into the new project, and get the business rule results aTomatically without having to reapply them.

  • You can copy an entity business rule from the Library into a dynamic entity. You can promote an entity business rule in a dynamic entity to the Library and associate it to a library entity.