locked
MDS modeling techniques RRS feed

  • Question

  • hi all,

    I have a couple modeling concerns, as they relate to MDS 2012:

    1. Is it possible/advisable to have just one entity created out of a table that has P/C relationships for *multiple* hierarchies?  

    Say I have a table with the following columns:

    HierarchyName varchar(10)
    ParentCode varchar(10)
    ChildCode varchar(10)

    where the same ChildCode may belong in multiple hierarchies, having the *same* or *different* parents?

    Currently, not seeing how this is possible, because the ChildCode (as far as MDS is concerned, needs to be unique across the entity)  our solution is to have one entity per hierarchy.  Is this the day to do it (creating one entity per hierarchy)? 

    2. Compound columns determining uniqueness:
    Say we have a table, such as below, where all 4 columns hold the uniqueness of the row:

    Code varchar(10)
    StartDate date
    StartTime date
    isActive bit

    Is this possible in MDS, without creating a large concatenated field (of the 4)? 

    It seems that MDS requires the CODE attribute to be unique so the only feasible way to implement multi-column uniqueness is to concatenate these fields, and then parse them out, after the fact, with a business rule or such.  Or, just create an "identity" key for the Code attribute and manage the 4 column uniqueness in a business rule. 

    thx a bunch for any feedback onto these modeling quandaries. :-)

    Cos


    • Edited by Cos2008 Wednesday, December 18, 2013 7:49 PM
    Wednesday, December 18, 2013 4:59 PM

Answers

  • 1) Multiple hierarchies are generally applied to the same single entity where the leaf type members are shared across each of the hierarchies.  For example, you can create 2 explicit hierarchies HierA and HierB on Entity1.  Each leaf member in Entity1 is assigned to a parent in each hierarchy. Note that the parents must be different in each hierarchy and the member codes must be unique across the entity.

    2) You can create a business rule that ensures uniqueness across a combination of attributes (like a compound key). In the BR designer, under Validation you will see a Must Be Unique action. With this action you can select one attribute as the "anchor attribute" for the business rule and place the other attributes in a list if you select the "in combination with the following" option. Not the easiest of things to find and build.

    Regards,

    Val


    Val Lovicz
    http://www.profisee.com
    val.lovicz@profisee.com
    As the original creators of Microsoft MDS, Profisee's Master Data Maestro provides a range of enterprise-grade functionality to ensure MDS project success.


    • Edited by Val Lovicz Wednesday, January 8, 2014 11:32 PM
    • Proposed as answer by Val Lovicz Wednesday, January 8, 2014 11:33 PM
    • Marked as answer by Cos2008 Friday, January 10, 2014 3:56 PM
    Wednesday, January 8, 2014 11:31 PM

All replies

  • 1) Multiple hierarchies are generally applied to the same single entity where the leaf type members are shared across each of the hierarchies.  For example, you can create 2 explicit hierarchies HierA and HierB on Entity1.  Each leaf member in Entity1 is assigned to a parent in each hierarchy. Note that the parents must be different in each hierarchy and the member codes must be unique across the entity.

    2) You can create a business rule that ensures uniqueness across a combination of attributes (like a compound key). In the BR designer, under Validation you will see a Must Be Unique action. With this action you can select one attribute as the "anchor attribute" for the business rule and place the other attributes in a list if you select the "in combination with the following" option. Not the easiest of things to find and build.

    Regards,

    Val


    Val Lovicz
    http://www.profisee.com
    val.lovicz@profisee.com
    As the original creators of Microsoft MDS, Profisee's Master Data Maestro provides a range of enterprise-grade functionality to ensure MDS project success.


    • Edited by Val Lovicz Wednesday, January 8, 2014 11:32 PM
    • Proposed as answer by Val Lovicz Wednesday, January 8, 2014 11:33 PM
    • Marked as answer by Cos2008 Friday, January 10, 2014 3:56 PM
    Wednesday, January 8, 2014 11:31 PM
  • thank you so much, Val!  -- I appreciate your feedback.

    Cos

    Friday, January 10, 2014 3:56 PM