web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Convert managed Entity...
Microsoft Dynamics CRM (Archived)

Convert managed Entity into Unmanaged.

(1) ShareShare
ReportReport
Posted on by Community Member

How to convert a managed Entity into an unmanaged one in MS CRM 2013?

I have an unused entity which was created  by mistake in Organisation Scope level  which was moved from source to target by mistake . We have this unused entity in a managed form in target . Is there any possible way to delete this managed entity ? 

Or 

Is it possible to convert managed into unmanaged in Target so as to enable removal .

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Aiden Kaskela Profile Picture
    Aiden Kaskela 19,696 on at

    Hi,

    You can't convert a managed entity to unmanaged, at least not in a supported way. I have been able to do this before with managed attributes hitting SQL directly but it's always risky and should be a last resort. If you want to banish the entity, your safest bet is to update your user's security roles so they don't have access to it - this will hide it from all navigation and advanced find views. The system admin will still see it, but if you change the display label to start with "z" or an underscore maybe, you'll move it to the bottom of the advanced find view and it'll be most out of the way.

    Hope this helps! I'd appreciate if you'd mark this as Answering your question.

    Thanks,

     Aiden

  • Community Member Profile Picture
    Community Member on at

    Hi Aideen , Thanks . We have been restricting this entity in security model as you have said , But the real problem is we have two versions of this unused entity with same schema name  in two different scopes - User and Organisation  with Organisation being created first and deleted and then again created with user scope , but the former one got by mistake deployed into Target even before it was deleted in source . So we need to delete the one in Target so as to send this new one .  We dont have any database access for this target.

  • Suggested answer
    Aiden Kaskela Profile Picture
    Aiden Kaskela 19,696 on at

    If you have a managed entity on your destination organization and it's not on the source environment, or it's a different type, you're going to have problems rolling out. I've had to deal with this in the past where we have a Dev environment and a testing environment.

    What I've done in the past is to delete the entity from Dev, then create a new solution on Testing, include just the problem entity, and bring that solution down to dev, then include the entity in your standard dev solution. Now both entities will be matching and you'll be able to roll out without a problem.

    Hope this helps! I'd appreciate if you'd mark this as Answering your question.

    Thanks,

     Aiden

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans