This is my first blog that has nothing to do with CRM. But it is very funny. Around 34435 people signed the petition to secure resources and funding, and begin construction of a Death Star by 2016. BC. By law , White House has to respond to any petition signed by more than 25000 people. Here is the official response by White House.
https://petitions.whitehouse.gov/response/isnt-petition-response-youre-looking .
<html xmlns="http://www.w3.org/1999/xhtml" > <head> <title>Untitled Page</title> <style type="text/css">html,body{font-family: Segoe UI, Tahoma, Arial;background-color: #d6e8ff;border: 0px; margin: 0px; padding: 0px;}</style> <script type="text/javascript" language="javascript"> //debugger; //get the context var Xrm = window.parent.Xrm; //get the current object id var oId = Xrm.Page.data.entity.getId(); //get the object type var oType = Xrm.Page.context.getQueryStringParameters().etc; //set Relationship Name var relName = getDataParam(); if (relName != "not found") { //building a url var sUrl = "/userdefined/areas.aspx?oId=" + oId + "&oType=" + oType + "&pagemode=iframe&security=852023&tabSet=" + relName; //get relative path with orgname as required var relativeUrl = Xrm.Page.context.prependOrgName(sUrl); window.location = relativeUrl; } else { noParams(); } //Most of this code is from sdk dataparams example function getDataParam() { //Get the any query string parameters and load them into the vals array var vals = new Array(); if (location.search != "") { vals = location.search.substr(1).split("&"); for (var i in vals) { vals[i] = vals[i].replace(/\+/g, " ").split("="); } //look for the parameter named 'data' and return relationship name for (var i in vals) { if (vals[i][0].toLowerCase() == "data") { var relationship = decodeURIComponent(vals[i][1]) relationship = relationship.replace(/\+/g, " ") return vals[i][1]; }//endif } //end for loop return "not found"; }//endif else { return "not found"; } }// end function function noParams() { var message = document.createElement("p"); message.innerText = "No data parameter was passed to this page"; document.body.appendChild(message); } </script> </head> <body> </body> </html>
<html xmlns="http://www.w3.org/1999/xhtml" >
<head>
<title>Untitled Page</title>
<style type="text/css">html,body{font-family: Segoe UI, Tahoma, Arial;background-color: #d6e8ff;border: 0px; margin: 0px; padding: 0px;}</style>
<script type="text/javascript" language="javascript">
//debugger;
//get the context
var Xrm = window.parent.Xrm;
//get the current object id
var oId = Xrm.Page.data.entity.getId();
//get the object type
var oType = Xrm.Page.context.getQueryStringParameters().etc;
//set Relationship Name
var relName = "lead_owning_user";
//building a url
var sUrl = "/userdefined/areas.aspx?oId=" + oId + "&oType=" + oType + "&pagemode=iframe&security=852023&tabSet=" + relName;
//get relative path with orgname as required
var relativeUrl = Xrm.Page.context.prependOrgName(sUrl);
window.location = relativeUrl;
</script>
</head>
<body>
</body>
</html>
I was trying to setup the security roles on teams instead of assigning security role to the individual users. The end result is that it does not work very well.
Here are the details of what happened.
I had a user with security role named “Manager”. Everything was working as expected. The user was able to create and update the entities defined in the security role. We decided to the create a team named “Manager” and assign the role to the team. I added the user to the team and remove the security role from the user. Here is what happened after that
I was able to open , create and update the entities as defined in the security roles until we created a new for form for an existing entity.
When I tried to open the newly created form for the entity, I received the following error message.
I had a look in the event viewer. It was showing the following warning message.
Exception message: SecLib::AccessCheckEx failed. Returned hr = -2147187962, ObjectID: 3be48aca-0f39-e211-bce1-005056b8253f, OwnerId: 9cc2541a-9137-e211-bce1-005056b8253f, OwnerIdType: 8 and CallingUser: 9cc2541a-9137-e211-bce1-005056b8253f. ObjectTypeCode: 2500, objectBusinessUnitId: bf221f51-8537-e211-bce1-005056b8253f, AccessRights: WriteAccess
The object type code 2500 represents the entity “User Entity UI Settings”. I checked the permissions on the entity. The user had the required permissions on the entity. The most annoying part was that I was able to open the existing form without a problem.
So I decided to look a bit deeper into the problem and here are my findings.
1. I created a new user and add the user to the team without assigning any role to the user.
I received an error message “Access Is Denied” every time I tried to open any entity form.
2. I added the same security role to the user as security role assigned to the team.
I tried to open account and contact entity form and I was able to open them without an error.
3. I removed the security role from the user again
I was able to open the entity forms I tried in step 2 but, I was unable to open the form for any other entity or different form for the same entity.
You have to have a security role assigned to the user to open any entity form minimum for the first time.
Every time you create an option set or a lookup field in CRM, the system creates 2 fields. For example if you create a lookup field named “new_contact”, the system will create the following 2 fields:
The first field is created as expected. But the system creates the second field automatically. If you ever looked into the filtered views, you must have noticed the extra name columns for lookup and option set fields. If you open a FilteredAccount view, you will notice primarycontactid and primarycontactidname columns. The primarycontactid column contains the guid of the primary contact and primarycontactidname contains the actual name of the contact.
In case of optionset field, the first field contains the integer value of the optionset and second field contains the optionset text value.
The problem is that the CRM UI does not display the second field. You won’t find primaryconactidname in the field’s grid of account entity.
To verify this behaviour, I created a lookup field name “new_contact” and then I tried to create a new field “new_contactname”. I received the following error message.
If you receive the “Duplicate Field Name” error, the reason can be a existing lookup or optionset field as explained above.
