Skip to main content

Dynamics CRM - The purpose of a manager

Purpose of the manager field

When I started to configure my first CRM organization a few years ago, one of the very first questions I asked myself was: "What's the purpose of the manager field?"




Hierarchy / org chart

Some system entities offer an out of the box hierarchy visualization, like account, position, product and user.


If you enter a manger for an user a hierarchy icon appears on the user form and in the user grid view, which allows to visualize an org chart, like below:


Hiearchy security

Dynamics CRM offers a hierarchy security model, which can be activated in the security settings. It is either based on the manager or the position you enter for a user in CRM.

Approval processes

The manager field can be used for approval processes. E.g. there could be a field with field level security on your form, which can only be edited by managers to approve a discount on a quote.


Additionally the manager could be notified via e-mail by a workflow, by sending a mail to your manager, after a discount has been entered.


Goals

A goal always consists of a goal owner and a goal manager. In my environment we have automated goal setup via Scribe. In that case we can easily set goal owner and goal manager.





There  might be even more, I have not listed here.







Comments

Popular posts from this blog

Power Automate Get absolute Sharepoint URL from document location

Document Locations If you enable Sharepoint document integration in your model driven apps, you can define for which entities the possibility to upload documents to sharepoint shall be offered and you can define a folder structure. Possible folder structures can either be based on account or contact, which means if you create child items (e.g. opportunities, activities, ...) sub folders are created below. If an entity is enabled for document management a "Files" tab is added to the form of your model driven app and as soon as you click on that tab a folder is automatically generated on Sharepoint. Once the folder has been created you have options to create new or upload existing file or to open the document location (folder) on Sharepoint: What happens behind the scenes is, as soon as you click on the files tab your model driven app checks, weither a "document location" for this item already exists, or not. The document location is an own entity in C

Send e-mails with a link to the record via Power Automate

Today we gonna have a look at how to send an e-mail with a link to a CDS record via Power Automate. In the good old classic workflows, you could directly reference the "record URL" from the dynamic data. But since UCI has been launched and you have the possiblity to target different apps, you already had to do a few more steps in the classic workflows as well. The URL to a CDS record consists of multiple things: CRM URL appid entity name record id So we will work this out one after the other. First we add a "List record" action to lookup the appid of the app, we target. We look for "model driven apps" and filter by the name of the app: Then we initialize a variable with the resulting app id: Then we initialize another variable and extract the CRM_URL: Then we fetch our records, where we want to send out a notification with a link, in this case we look for workorders fullfilling certain criteria: Now we compose the record URL: As a next step we create a new

Working with Optionset lables in Power Automate

Connector Types Power Automate currently offers 3 different connectors, to connect Power Automate with your Dynamics 365 instance: Dynamics 365 Common Data Service Common Data Service (current environment) Today we will look on ways how to retrieve option set labels via the different connectors, for our sample accounts: Dynamics 365 This connector should not be used any more , since in April 2019 it has been announced as being deprecated. https://flow.microsoft.com/en-us/blog/nine-new-connectors-in-april-and-improved-visibility-into-trigger-failures/ With the Dynamics 365 connector it was quite easy to work with optionsets, since it offered both the optionset value (int) and the optionset label (name) in the dynamic content: And here we go, these are our results: Common Data Service Since the Dynamics 365 connector has been deprecated, this is the connector you should use. If you perform a "Get record" or "List records&