WTF did Microsoft do with the subscription views in SQL 2012 MDS? What WAS called the [VersionMember_ID] in a subscription view is now simply [ID].
Here's my issue; I have hundreds of subscription views that are consumed by other down-stream processes and they all rely on the [VersionMember_ID] field in the views. Now that the database has been upgraded to MDS 2012, those same subscription views expose a column named [ID]. This breaks all my down-stream processes.
I consider this an EPIC FAILURE of the design team of MDS. They were kind enough to keep the original batch based staging tables for backward compatibility concerns, but to go an REMOVE a column from a subscription view is ABSOLUTELY UNEXCUSABLE.
I mean, really, how hard would it be to expose the [ID] column TWICE in every subscription view, once as [ID] and once as [VersionMemver_ID]. If you then wanted to use the view in backward compatibility mode, you could use the [VersonMember_ID] column. If you are going strictly with MDS 2012, use the [ID] column.
Todd C - MSCTS SQL Server 2005, MCITP BI Dev 2008 Please mark posts as answered where appropriate.