Skip to main content

Can you explain the difference between Share and Assign in MSCRM?

Assigning Records

Assigning records is the act of changing the owner of the record.  Depending on security settings, assigning records may impact who can view or edit the record.  In order to assign records to a new owner, you can either
  1. Change the Owner on the record on the form.
  2. Click Assign on the Command Bar while viewing a record.
  3. Select one or more records from a grid view, and on the Command bar, click Assign.
Assigning records can also trigger workflows, such as a notification that a record has been assigned to you.

Sharing Records

When security settings prevent some users from seeing or editing all records in the Dynamics 365, it may be necessary to share records that require collaboration across teams.  When sharing, you can share the view, edit, assign, or delete rights as long as you have them yourself.  In order to share records,
  1. While viewing the record or while selecting one or more records on the grid view, click Share under the ellipsis on the Command Bar.
  2. Individually select the rights that the users will have to the shared records OR select Toggleon the left to toggle on/off all rights.
  3. Click Share.
The individuals who have rights to see the record are not visible on the record.  In order to see them, you must click Share again on the Command Bar.  From there, you may add or remove rights.
Labels:

Comments

Post a Comment

Popular posts from this blog

Microsoft Dynamics 365 CRM Troubleshooting Solution Import Errors

Remember when CRM life was so much simpler that solutions did not yet exist? If you had separate development and production environments and you wanted to move your customizations, you simply clicked  Export Customizations  and voila! It was done. Those were the days. Nostalgia Warning – in case you’ve forgotten, here’s a screenshot to jog your memory: With CRM 2011, the concept of solutions was introduced, giving us a new set of powers – by picking individual entities, workflows, etc., we now had the ability to group together and move only those customizations we wanted to include in our solution. The next great solutions advancement came with CRM 2016: we can now select specific components within each individual entity – so instead of moving the entire contact entity, for example, we have the option of moving only a certain view or field within the entity. And we can do this without having to hack the xml in the zip file. (By the way, if you want to learn more abou...
Post a Comment
Read more

How to Filter SubGrid Lookup view in Dynamics 365 CRM

How to Filter SubGrid Lookup view in Dynamics 365 CRM.  Please check the comments in the below code and do follow the steps accordingly and call the  filterSubGrid() funtion on onload. var LastQuery = ""; function filterSubGrid() { debugger; setSubgridLookupFiltering(); } function AddLookupFilter(entity_type, customFilter) { var subgridLookup = Xrm.Page.getControl("lookup_Contacts_Participants"); subgridLookup.addCustomFilter(customFilter, entity_type); } function setSubgridLookupFiltering() { var subgridAddButtonId = "Contacts_Participants_addImageButton"; //Try to get the element from both the current and the parent document. var subgridAddButton = document.getElementById(subgridAddButtonId) || window.parent.document.getElementById(subgridAddButtonId); //This script may run before the subgrid has been fully loaded on the form. If this is the case, //delay and retry until the subgrid has been loaded. if (subg...
Post a Comment
Read more

How to prevent record from saving in Dynamics CRM using Javascript

  From time to time you might need to add some validation to the save event of an entity, this actually used to be an approach I would use on a regular basis but since the introduction of business rules have found myself doing this less and less. But still, knowing the ability is available is handy. When you define the onsave event function, you must tick the “Pass execution contact as first parameter” option. (See below) Having done that you can create an onSave function with code similar to the example I have shown below. Note forgetting the “(context)”, which will take the context parameter allowing you to prevent the save when needed. function onSave(context) { var saveEvent = context.getEventArgs(); if (Xrm.Page.getAttribute("telephone1").getValue() == null) { // *** Note: I am using an alert for testing a notification maybe better! alert("Put in a phone number!"); saveEvent.preventDefault(); } } Note: This simple example might be better achi...
Post a Comment
Read more