Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics CRM (Archived)

What is the best approach during solution deployment to solve the issue when the attribute with same schema name but different Data types in source and target instances?

Posted on by 1,825

Hi Experts,

I am looking for the best approaches while deploying managed and unmanaged solutions:

When the attribute schema name is the same but the data type is different in source and target instances.
In case if I am going to delete the field in target instance what would be the solution to remove the dependencies in the managed solution.

The below approach I have followed:
I removed dependencies manually. And deleted the field.


Thanks
Hemant

*This post is locked for comments

  • Verified answer
    Mahadeo Matre Profile Picture
    Mahadeo Matre 17,021 on at
    RE: What is the best approach during solution deployment to solve the issue when the attribute with same schema name but different Data types in source and target instances?

    Hi Hemant,

    As Arun mentioned remove of managed solution will delete all components including the attributes, so you will lose your all data related to custom entities and custom attributes in managed solution.

    You need to manually delete attribute from system and then using import solution, you can create attribute.. and then you need update data in that field.

  • Hemant Kumar Sahu Profile Picture
    Hemant Kumar Sahu 1,825 on at
    RE: What is the best approach during solution deployment to solve the issue when the attribute with same schema name but different Data types in source and target instances?

    Thank you Arun for your reply.

    In case when we uninstall the managed solution we will lose the data.

    Regards

    Hemant

  • Verified answer
    Arun Vinoth Profile Picture
    Arun Vinoth 11,613 on at
    RE: What is the best approach during solution deployment to solve the issue when the attribute with same schema name but different Data types in source and target instances?

    Solution cannot be used to remove/delete the attribute in the target system. So removing the dependencies manually & deleting it is the only option.

    If it’s managed solution, then deleting solution will remove all the components including the attributes. So you can import the latest managed solution with the new attribute (same name) with correct datatype works.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,269 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,198 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans