none
Restricting MDS member Update

    Question

  • Guys, I want to avoid bad data coming again and again from source after  validating and updating member in a entity.

    Let me explain.

    For particular member  city coming as 'XYZ' from source which is wrong.

    So we updated value from explorer with correct value "Boston".

    Since data load from source is happening through ETL, next load bring again wrong value into my member city attribute.

    Since I cannot update my source data, I need to implement a work around in ETL/T-SQL to identify previous updated value for attribute for members and update value with MDS current value only. 

    Any help, will appreciated.

    Friday, February 28, 2014 6:27 PM