Answered by:
CRM 2011: Manager Field behavior

Question
-
Hi all,
Could anybody please explain what does the manager field in the user form behave this way ?
The field is read only and cannot be enable using field properties form ! Also in order to update it we must use the change manager button in the ribbon, it cannot be auto populated using javascript based on other form values.
What can I do in order to populate the manager of a user based on another field value in the form, I mean the field is populated successfully but after saving the form the value disappears, I tried to set the submit mode to always with no luck.
Please advise..
- Edited by Mostafa Moatassem Wednesday, December 5, 2012 10:42 AM
Wednesday, December 5, 2012 10:40 AM
Answers
-
Because you could assign the system user to itself, e.g. Joe Bloggs is Joe Bloggs Manager. It's not allowed. This applies to any type of recursive behaviour, you cannot add a lookup on an entity to itself.
MS CRM Bing'd - http://bingsoft.wordpress.com Dynamics XRM Tools CRM 4 to CRM 2011 JavaScript Converter Tool CRM 2011 OData Query Designer CRM 2011 Metadata Browser CRM Forum Guidance This information is extremely inaccurate. Our system has a lot of self-referential relationships and just to verify I just added a lookup on user to itself. CRM 2011 has no problem at all with that. These lookups automatically restrict you from picking the record you are on, so no danger of recursive behavior.
That being said, I don't really use the manager field. There are restrictions around it though that require a manager to be in the same business unit or a hierarchically higher business unit than the user, so I'm guessing that is why they restrict you from directly changing it.
- Proposed as answer by DavidBerryMVP, Moderator Sunday, March 10, 2013 4:15 AM
- Marked as answer by Mostafa Moatassem Sunday, March 10, 2013 9:00 AM
Friday, March 8, 2013 9:13 PM -
Justin is correct. Unfortunately, my colleague Rhett, is not. This behavior is very tightly controlled because there are limitations about where the Manager must be in the BU structure, in relation to the User. This has absolutely nothing to do with self-referential relationships or circular references. Additionally, I most certainly can add a reference from System User to System User.
The Manager relationship is generally only useful for out-of-the-box reports, and little else. It does not confer any security privileges (although it may have, prior to CRM 3.0, as many of these features were designed and implemented once, and often never updated or revisited), and I haven't found another out-of-box entity or process that depends on it. You'd be well within your rights to consider replacing it with a new relationship that behaves the way you wish.
Dave Berry - MVP Dynamics CRM - http:\\crmentropy.blogspot.com Please follow the forum guidelines when inquiring of the dedicated CRM community for assistance.
- Proposed as answer by DavidBerryMVP, Moderator Sunday, March 10, 2013 4:26 AM
- Marked as answer by Mostafa Moatassem Sunday, March 10, 2013 9:03 AM
Sunday, March 10, 2013 4:26 AMModerator
All replies
-
Please explain more, what is the risk of assigning the manager field manually ?Monday, January 7, 2013 2:24 PM
-
So what about creating a custom manager field and adding a validation to prevent assigning it to the current user ?Monday, January 7, 2013 5:21 PM
-
Because you could assign the system user to itself, e.g. Joe Bloggs is Joe Bloggs Manager. It's not allowed. This applies to any type of recursive behaviour, you cannot add a lookup on an entity to itself.
MS CRM Bing'd - http://bingsoft.wordpress.com Dynamics XRM Tools CRM 4 to CRM 2011 JavaScript Converter Tool CRM 2011 OData Query Designer CRM 2011 Metadata Browser CRM Forum Guidance This information is extremely inaccurate. Our system has a lot of self-referential relationships and just to verify I just added a lookup on user to itself. CRM 2011 has no problem at all with that. These lookups automatically restrict you from picking the record you are on, so no danger of recursive behavior.
That being said, I don't really use the manager field. There are restrictions around it though that require a manager to be in the same business unit or a hierarchically higher business unit than the user, so I'm guessing that is why they restrict you from directly changing it.
- Proposed as answer by DavidBerryMVP, Moderator Sunday, March 10, 2013 4:15 AM
- Marked as answer by Mostafa Moatassem Sunday, March 10, 2013 9:00 AM
Friday, March 8, 2013 9:13 PM -
Justin is correct. Unfortunately, my colleague Rhett, is not. This behavior is very tightly controlled because there are limitations about where the Manager must be in the BU structure, in relation to the User. This has absolutely nothing to do with self-referential relationships or circular references. Additionally, I most certainly can add a reference from System User to System User.
The Manager relationship is generally only useful for out-of-the-box reports, and little else. It does not confer any security privileges (although it may have, prior to CRM 3.0, as many of these features were designed and implemented once, and often never updated or revisited), and I haven't found another out-of-box entity or process that depends on it. You'd be well within your rights to consider replacing it with a new relationship that behaves the way you wish.
Dave Berry - MVP Dynamics CRM - http:\\crmentropy.blogspot.com Please follow the forum guidelines when inquiring of the dedicated CRM community for assistance.
- Proposed as answer by DavidBerryMVP, Moderator Sunday, March 10, 2013 4:26 AM
- Marked as answer by Mostafa Moatassem Sunday, March 10, 2013 9:03 AM
Sunday, March 10, 2013 4:26 AMModerator -
I apologise, I pride myself in the information I share and I'm unable to explain what I was thinking of this day. Rhett
MS CRM Bing'd - http://bingsoft.wordpress.com Dynamics XRM Tools CRM 4 to CRM 2011 JavaScript Converter Tool CRM 2011 OData Query Designer CRM 2011 Metadata Browser CRM Forum Guidance Sunday, March 10, 2013 10:24 AMModerator