Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
Is there any formal reason why you should use a Role to determine the account manager function, rather than use the Owner property?
I'd prefer to use a Role, as we'll use other Roles for various reasons (Technical Lead, etc) so it makes sense for them all to be there. We also *may* foresee having two account managers for larger clients.
However the Owner field is so easy to use and access, and can be seen on page one of each account, and is always available views. It seems much easier to use the Owner field. However it does prevent us from having multiple account managers.
Thoughts? What are you all doing?
A security role defines how different users, such as salespeople, access different types of records. It's a list of users with the same permissions follow your business requirement.
An owner is only a field which on behalf of the user who created (or be assigned) the record. The owner may be salesperson who has many accounts, so it's not a good way to use owner field to be salesmanager.
If you use roles to determine the account manager, you could have multiple account mangaers (a role contains many users), and you could configer the permissions of the role, like "read, edit, delete, create" of an entity.
Here is the DOC about security role for your reference.
Hope it helps.
Business Applications communities