MDS 2012 Deployment Issue with domain attributes RRS feed

  • General discussion

  • Scenario:

    We made the following changes on  one of the entities on MDS SIT:

    1)Added four new columns.
    2)Changed attribute type from Free Form to Domain Based (for attribute Financial Classification).

    To reflect these Changes on UAT we initiated deployment for MDS. The MDS deployment packaging was done using MDS wizard(without data).The deployment of the same was done using  MDSDeployTool. (deploy update)
    The deployment of MDS package on UAT was completed successfully.

    Observation post deployment on UAT:

    1)Four new columns created successfully.
    2) Change in attribute type from Free Form to Domain Based (for attribute Financial Classification)-Failed

    The concerned attribute still appears to be a free form attribute on UAT

    Why does the domain based attribute not reflect in UAT

    Tuesday, November 25, 2014 10:38 AM

All replies

  • Can the values of the attribute column which was changed be different in SIT and UAT?

    Is there a possibility that the in UAT you have a attribute value which cannot be successfully converted to new DBA.

    Can you also try using MDSDeployTool editor and deploy entity by entity starting with DBA(Financial Classification) entity?

    -Nithesh Shetty Software Engineer, C & E -> IMML -> MDS, Microsoft.

    Tuesday, November 25, 2014 10:44 PM
  • Actually, I found that initially in UAT, my attribute type was free-form. And we had to change it to Domain based.

    Since there is no option of changing attribute type from MDS Web UI and only through excel-addin. (As per the link below). We deleted old attribute, subscription view from SIT, created new domain based attribute with same name.


    So now, the problem is how to deploy this change in UAT /Prod. As MDS deployment package will never delete master data (members) or metadata (attributes, entities, models).

    Though we used deployupdate (using utility) and still our deletions and new attribute were not deployed. The old attribute persisted to be free-form in UAT.

    How to resolve this?

    So its a typical case which happens to be a frequent change. Initially the attribute was designed to be free-form and after model deployment, now there is a change expected to make it to domain-based. How do you deploy these changes across environments?


    Wednesday, November 26, 2014 9:34 AM
  • Indira, is this still an issue?


    Ed Price, Azure & Power BI Customer Program Manager (Blog, Small Basic, Wiki Ninjas, Wiki)

    Answer an interesting question? Create a wiki article about it!

    Monday, January 19, 2015 7:55 AM
  • I have the same issue. 

    1. Initially the attribute was fee-form in DEV environment. Deployment to QA as free-form.

    2. Changing the attribute in DEV to domain-based. No problems encountered.

    3. Deployment of change to QA: doesn't work. Attribute remains free-form in QA.

    How can I solve this?


    Friday, April 22, 2016 9:45 AM