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