| title | Create a Derived Hierarchy | ||
|---|---|---|---|
| ms.custom | |||
| ms.date | 03/01/2017 | ||
| ms.prod | sql | ||
| ms.prod_service | mds | ||
| ms.reviewer | |||
| ms.technology | master-data-services | ||
| ms.topic | conceptual | ||
| helpviewer_keywords |
|
||
| ms.assetid | fec653c4-11cc-46a2-8dd8-b605341ebb40 | ||
| author | lrtoyou1223 | ||
| ms.author | lle |
[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md-winonly]
In [!INCLUDEssMDSshort], create a derived hierarchy when you want a level-based hierarchy that ensures that members exist at the correct level. Derived hierarchies are based on the domain-based attribute relationships that exist in a model.
Note
If a domain-based attribute value doesn't exist for a member, the member is not included in the derived hierarchy. See Require Attribute Values (Master Data Services) to require a domain-based attribute value for all members.
To perform this procedure:
-
You must have permission to access the System Administration functional area.
-
You must be a model administrator. For more information, see Administrators (Master Data Services).
-
In [!INCLUDEssMDSmdm], click System Administration.
-
From the menu bar, point to Manage and click Derived Hierarchies.
-
On the Derived Hierarchy Maintenance page, from the Model list, select a model.
-
Click Add.
-
On the Add Derived Hierarchy page, in the Derived hierarchy name box, type a name for the hierarchy.
[!TIP]
Use a name that describes the levels in the hierarchy, for example Product to Subcategory to Category. -
Click Save derived hierarchy.
-
On the Edit Derived Hierarchy page, in the Available Entities and Hierarchies pane, click an entity or hierarchy and drag it to the Drop Parent Here in Current Levels pane.
-
Continue dragging entities or hierarchies until your hierarchy is complete.
-
Click Back.
Derived Hierarchies (Master Data Services)
Derived Hierarchies with Explicit Caps (Master Data Services)
Domain-Based Attributes (Master Data Services)