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) / Assigning lead to user...
Microsoft Dynamics CRM (Archived)

Assigning lead to user with error

(0) ShareShare
ReportReport
Posted on by Community Member

Hi guys,

I'm trying to assign a lead to an user from a different business unit. It is throwing an Access Denied error but once you click ok the assignment works. It's very confusing for people and it should either be the error and not assign it or no error and assignment to work. I know it was discussed before but there was no decent explanation for what is happening. Both users share the same security role. Upgraded to 2016 5 months ago, and this wasn't happening in 2013 version.

 Shared security role below.

7848.lead2.PNG

*This post is locked for comments

  • Suggested answer
    tw0sh3ds Profile Picture
    tw0sh3ds 5,600 on at
    RE: Assigning lead to user with error

    Bobby,

    Ok it's good we have cleared that out :)

    Setting assign to Parent-Child would have the impact that users will not be able to assign the record and no longer have "Read" access to it (because Assign and Read would be on the same level) But from your last post I assume that this is correct scenario - users can assign the record to whomever they want, and can loose access to that record? If yes, then if you don't want this error you should share the record to original owner (and maybe then create a mechanism to unshare it if you wish, somebody mentioned that earlier). The best way would be to redirect user from the form after assignment - I guess this should be possible with some ugly JS/plugin combo hack.

    Are the new users in your company trained on some workshops or they just receive some user manual? If it's a manual I would add a chapter about security with also some tips to assign records from the entity view rather than entity form (because of such things)

  • Community Member Profile Picture
    Community Member on at
    RE: Assigning lead to user with error

    Prashant, the only thing showing in the log file is the missing Read privilege for current entity. I already have Parent-Child set for it. If I change it to Org it will work without error message but I don't really want to give users Org access.

  • Community Member Profile Picture
    Community Member on at
    RE: Assigning lead to user with error

    :) Pawel this discussion got a little bit out of control. I didn't feel offended and for sure my intention was not to make you feel guilty for offending me. I just got the feeling from your post that I'm facing a sales person who's trying to hard sale a product and I'm not convinced about the benefits of it(I'm pretty sure you know that feeling too). Other people make suggestions to overcome the issue and you are trying to convince me to accept it the way it is. I might have got the wrong idea so I apologize if I did(this post is starting to look like a "forgive me for I have sinned" post now). It might be my testing background maybe that makes me strongly disagree that the situation is being handled correctly at the moment?

    Hope this clarifies it so we can have a normal discussion moving forward.

    Would it make a difference if I go for Deep assign when currently is Global and not working?

    I would rather prefer, if possible, to avoid sharing the record with the original owner after assignment. Although I can't see another workaround for this at the moment.

    Thank you

  • tw0sh3ds Profile Picture
    tw0sh3ds 5,600 on at
    RE: Assigning lead to user with error

    Bobby,

    I respect your opinion, I even gave you the link to site where you can create your idea how to improve this and let the community vote for it. You can also report this as a bug to Microsoft support.

    You did not respond to my other questions - is this correct that users have assign on Org level and Read on Deep? Why not set Assign on Deep?

    Should the initial owner still be able to read the entity? If yes than why not enable "Share with original owner" setting?

    I'm sorry, if you felt offended, it was not my intention. We are all just trying to help you, but I just no longer understand what you are expecting from us in this topic. Should we all complain that this is a bug? We are all trying to suggest you something and also trying to understand the design of your system by asking questions to help you redesign something so that it would be more user friendly because we cannot do anything about how CRM handles such scenarios.

  • PS Profile Picture
    PS 23,577 on at
    RE: Assigning lead to user with error

    Can u download the log file, when u see the error

  • Community Member Profile Picture
    Community Member on at
    RE: Assigning lead to user with error

    Pawel, I respect your opinion and you should respect mine.

    When you access a record and you have the Owner field that sais it's yours, then you click assign and try to assign it to one of your colleagues and all you get is a big fat access denied message but in the same time the Owner field sais you are the owner and even after you click OK to accept the Access Denied message you are still on the same page and you see that nothing changed to the record and you're still the owner of it, you can't convince me this is correct system behavior. I'm not saying the logic is wrong all I'm saying is the situation is not correctly handled.

    As you can see in my initial post, Assign is set at the Org level. The problem here is with Read privileges.

  • Verified answer
    Nuno Profile Picture
    Nuno 2,005 on at
    RE: Assigning lead to user with error

    Hi Bobby,

    You may develop a plugin on Assign (post-operation) message which implements the logic: when user A assigns a lead to user B, share (read access) the lead with user A.

    This way user A will not get the error message on its form.

    Then starts a workflow that waits some timeout (e.g. 10 minutes, time excepted to the user move out from this form) and after that remove the access to record granted with sharing.

  • Suggested answer
    tw0sh3ds Profile Picture
    tw0sh3ds 5,600 on at
    RE: Assigning lead to user with error

    Hi,

    It was like that since I remember (so at least CRM 4.0). The scenario that you describe is really rare (user can assign his record to a user in different BU but can't read this record) so maybe nobody just reported this to Microsoft as a bug. There is this portal:

    crmideas.dynamics.com/.../dynamics-crm

    maybe it's a start, but for me and I think a lot of other people this is not a bug, this is working totally fine, just requires explaining the users how security in CRM works, so that they understand what is happening.

    Also I think that maybe it worked in older system because you had "Share reassigned records with original owner" option enabled. So that user did not loose access to the record after reassigning.

    You explained that you can't give user Org rights, but why can't you give Deep rights for Assign?

    Also why it's so hard to understand for the users that they loose access for the record after assigning it to different BU? For me it's a good thing, if there was no error maybe they would not realise that they just loose access to the record. Now it's clear for them.

  • Suggested answer
    PS Profile Picture
    PS 23,577 on at
    RE: Assigning lead to user with error

    You can create a real time workflow to stop this

    Run on lead assignment

    Check conditions

    If lead owning business unit doesn't equal to created by/ modified by users  business unit

    Stop workflow with status equal cancel and set message

  • Community Member Profile Picture
    Community Member on at
    RE: Assigning lead to user with error

    Hi Pawel,

    I can't give Org Read rights as child BU shouldn't see each other. And on top of that I also have 2 different departments. So that means I have to train everyone to forget about their very familiar and team customized dashboards and to start using View Level instead.

    As a developer I can live with it and accept it. But as an end user this is hard to digest. I think this is either a huge mistake that MS didn't take in consideration or just a bug for the newest version. It's confusing and frustrating people. You could have been thrown out of the record just after assignment, or something else(but a different solution). I'm pretty sure this wasn't the same in 2013.

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

Daivat Vartak – Community Spotlight

We are honored to recognize Daivat Vartak as our March 2025 Community…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Kudos to the February Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,516 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,432 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans