[nQSError: 15019] Table Calendar is functionally dependent upon level Month, but a more detailed child level has associated columns from that same table or a more detailed table.
Where It Happens
I encountered this error while trying to create Calendar Hierarchy as shown:
Reading the table name in question from our error message, we go to the Business Model & Mapping (BMM) and examine the logical Calendar table.
Why It Happens
Consistency check is complaining about our logical Calendar Table having more than one key in BMM Layer. This error seems counter intuitive to me as I all these keys depending which aggregation table I would like used depending on granularity desired.
I am certain my questions will be answered as I continue working on this RPD.
Removing this error (and additional ones for all extra keys in Calendar Table) required removing keys until only lowest key was left.
To get the sought after
And allowing us to save our model.