What the heck am I talking about? “Business Unit” ownership!? That’s not even a thing:
That’s more or less what I replied in the community forums to somebody who was asking about “business unit” ownership.
And yet, it does exist, even if it’s not something you can set up for your own custom entities:
You will find it on MSDN, too:
Entities that belong to a business unit. These entities have an attribute named owningbusinessunit.
Although, it seems even Microsoft itself got confused since they are mentioning owneingbusinessunit attribute which is NOT there for such entities. There is busineeunitid:
Owningbusinessunit is, actually, an attribute that you will find in the user/team owned entities. Such as an account entity, for example.
So what does all this mean, in practice?
Well, here is the thing.. When creating a team, or any other business unit – owned entity through the SDK, we have to set that businessunitid field. Otherwise, there will be an error:
An error has occurred: Expecting business column to be set for Creating business owned entities, business column is null
And, also, when setting up security, the minimum permission depth for such entities is “Business Unit”:
Every user in the business unit that owns the record will have access, and there is no way to make it more granular (user-level). Interestingly, that’s one of the caveats of the security model I used to notice occasionally, and, then, mostly used to dismiss as some strange quirk. Turned out there is an explanation.