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) / Change Entity Ownershi...
Microsoft Dynamics CRM (Archived)

Change Entity Ownership without loosing Data

(0) ShareShare
ReportReport
Posted on by Jigar Bhatt 537

Hello All,

Today we are at stage where we need to create 2 Business Unit in our existing System. Also we need to segregate Data like Product, Competitor, Email etc based on Business Unit. We have created 2 Business Unit in our existing System and we are able to segregate Data like Account, Quote , Order etc based on Business Unit. But we also need to segregate Product, Competitor based on Business Unit. We have tried various ways to achieve this without loosing our existing data but haven't achieve this.  

We have also identified that Ownership at Entity level is need to be set as "User or Team" to segregate data based on Business Unit. We have tried to change Ownership for Product, Competitor but it's Read-Only so we can't change from UI as well as from Back end.

Please suggest me a way to achieve this without loosing our existing Data.

Thanks & Regards,

Jigar

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Guido Preite Profile Picture
    Guido Preite 54,086 Moderator on at

    Product and Competitor as system entities and they cannot be changed to be "User Owned". Your only way is to create custom entities for Product and Competitor and use them inside your processes. Keep in mind that Product is connected practically everywhere on the sales pipeline, so you need to check if you really need to have "User Owned" products or not.

  • Suggested answer
    ashlega Profile Picture
    ashlega 34,477 on at

    Hi Jigar,

     adding to Guido's answer.. You can't make those two entities user-owned, but, normally, there are only two reasons to segregate data that way:

    - Security

    - Filtering

     From the security standpoint, I'm not sure if you are concerned about the visibility of that data (not sure why would those two entities be so important from that perspective), or if you are more concerned about the protection of that data (which would make sense if you did not want users in one business unit to update records in another business unit). You can still implement that kind of "protection" using a plugin, for example (deploy an "onupdate" plugin.. or a real-time workflow.. that will check if current user is allowed to update the product).

     Then, you might work on the visibility and filtering: create different views, and, if it's not enough, create a pre-RetrieveMultiple plugin to automatically add some filter condition based on the business unit of the user queries products/competitors

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