i'm seeing incorrect attribute member names in my degenerate dimensions.
the dsv looks like this:
SO records, AR records, and Customer records are all associated with a Location. SO and AR records are also associated with a Customer. in some cases, the SO or AR record LocationKey is different from the LocationKey of the customer record that
a SO or AR record is associated with.
when i create a cube and dimensions based on this dsv, it seems like initially everything is fine. however, inevitably i eventually see the following:
the AR and SO degenerate dimensions each have a Location attribute, with the fact table LocationKey column as the key, and the Location table LocationName column as the Name. at some point, the attribute member names will begin to appear as the Location
name that is associated with the LocationKey from the Customer table, rather than the appropriate fact table (AR or SO). it seems that this begins to happen after the relational database is updated. that process generally consists of deleting all fact
table rows and repopulating. when this problem appears, "Process full" on dimensions, partitions, measure groups, or the cube does not seem to resolve the problem.
i witness this error
View Complete Post