We ran across an issue with a client attempting to use one of our modules in a Site that belongs to a Site Group.  After testing, we discovered that our module can no longer obtain a list of valid users that belong to a particular Security Role via the DNN API call GetUsersByRoleName().  It works perfectly when on a Site not belonging to a Site Group.  Has anyone ran into this issue?  If so, what did you find as a resolution.  It appears to be a bug in the API.  Any insight would be greatly appreciated.

Thanks,

David

---

---

nvisionative, Inc.
Corporate Website  |  Facebook Page  |  Twitter Page

I am having a hard time believing nobody has ran into this issue by now.  ;-)  If you have ANY insight, I would really love to hear from you.

Thanks,

David

---

---

nvisionative, Inc.
Corporate Website  |  Facebook Page  |  Twitter Page

I was able to reproduce this, and will log this as a bug.

Luckily there is a workaround available, by using a different API call. As you may have noticed the Security Roles feature correctly reports members of roles that are unique to a member site. This is because the Security Roles features uses a different API call for that.

To explain, this is how I tested the behavior on the grouped portal:

            var roleController = new RoleController();

            Repeater1.DataSource = roleController.GetUsersByRoleName(PortalId, "Testrole1");
            Repeater1.DataBind();
            Repeater2.DataSource = roleController.GetUserRoles(PortalId, null, "Testrole1");
            Repeater2.DataBind();

The call to GetUsersByRoleName will fail, but the call to GetUserRoles, passing a null value for UserName gives a correct result. Please be aware that the objects that are returned are not UserInfo objects, but rather UserRoleInfo objects, so this is not a one to one workaround, some extra coding needs to be done.

---

Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: