MB2-700 Dynamics CRM 2013 Applications Certification Helper – Question#1

Which two record types require a reference to the subject tree? Each answer presents part of the solution. (Choose TWO)

A. Sales Attachments

B. Case Resolution Activity

C. Cases

D. Sales Literature

E. Knowledge Base articles

Read the rest of this entry

Microsoft CRM 2016 Interview Questions

Q. What are the new features introduced in CRM 2016

Q. Explain the differences between enhanced SLA vs Standard SLA

Q. Explain the functionality of each of the below marked services in Microsoft CRM 2016 Read the rest of this entry

‘First Response By’ and ‘Resolve By’ fields are not getting populated on case form for enhanced SLA

When you implement SLA feature in CRM 2015/2016 you might worry about these fields as they would be filled only based on the SLA type – ‘Standard’. You may remove the fields from the Case form depends on the SLA type (‘Enhanced’) you opt for the CRM setup.

 

If you enable the standard SLA, the below fields would be populated with values: Read the rest of this entry

How to set default Entitlement during Case Creation in CRM 2016?

Before CRM 2015 Update, users had to set the entitlement to a case record manually and as with the latest Microsoft CRM update, it can be automated.

 

An entitlement can be set as a ‘Default Entitlement’ for a customer and thereafter when a case is created for the customer, which entitlement will be assigned to the case automatically which saves service user’s time. Read the rest of this entry

How to setup Routing Rule in CRM 2016/2015/2013 Update

In versions prior to CRM 2013, an entity could only be routed to default queue of the owner of the record when record is created or assigned. For any other conditional routing, custom development was the way to go.

Now with CRM 2013 update and above versions, we can configure rules to automate routing of Cases. At the moment this feature is only available for Case Entity.

 

Create Routing Rule Set:

  1. Go to Settings->Service Management->Routing Rule Sets

1

2. Create a new Routing Rule Set. One Routing Rule Set can have multiple rule items. Provide the Routing Rule Set Name and save the record to create rule items under this rule set. Read the rest of this entry

Navigation Bar change in CRM 2016/2015 update1

Navigation Bar in Microsoft CRM has a new change introduced in CRM 2016 (also CRM 2015 update 1). This is now more user friendly and options are more easy to choose from.

The tiles are smaller, so more fit into a grouping, while the bar at the top is wider and easier to see. These size changes make this navigation style easier to use on mobile devices like cellphones and tablets, and the group arrangement allows for faster access to the areas you’re looking for.

NewNavBarChangeCRm2016.png

How to upgrade a CRM 2015 multi-tenant deployment to CRM 2016?

By running the setup file for CRM 2016, you can upgrade one organization and rest of the organizations would be disabled automatically. After the successful upgrade of first Organization in the server, other organizations need to be upgraded from ‘Deployment Manager’.

 

In the current scenario, I have CRM 2015 server with two organizations ‘Demo’ and ‘Demo2’.

  • Select any Organization to be upgraded while running the CRM 2016 setup

1     2

  • Organization ‘Demo2’ alone is upgraded to CRM 2016. Organization ‘Demo’ is not upgraded to 2016 and is disabled automatically. It needs to be upgraded from Deployment Manager.

3

  • Open the ‘Deployment Manager’. Clicking on ‘Upgrade Organization’ will pop up the Upgrade Organization Wizard.

4

  • Select ‘Upgrade’

5

  • Organization ‘Demo’ is upgraded to CRM 2016

6

Unable to get property ‘firstChild’ of undefined or null reference – Error accessing Microsoft CRM

You might have received this annoying popup error while accessing Microsoft CRM. You might wonder if there is anything wrong with the Jscript customization in your solution! This is actually a browser related problem and you can fix it quickly.

Resolution: Add the CRM url to the ‘Trusted sites’ list and you would not get this issue. Its related to the activex control access.

How to setup Hierarchy Security in CRM 2015?

Hierarchy Security is a new feature introduced in CRM 2015. It makes the security architecture of CRM 2015 more flexible.

Common facts about Hierarchy Security

Before explaining how to setup hierarchy security in CRM 2015, I would like to mention few facts about Hierarchy Security.

  1. You can enable or disable hierarchy feature anytime from Settings>Security>Hierarchy Security
  2. Hierarchy feature can either be enabled on Manager Hierarchy or custom Position Hierarchy – cannot be enabled on both at the same time
  3. Hierarchy Depth is being used to limit the levels of access
  4. A manager or supervisor would inherit Read, Write, Append and Append To access on records owned by direct reports or owned by teams where direct reports are members in it
  5. A manager or supervisor would inherit only Read access on records owned by indirect reports or owned by teams where indirect reports are members in it
  6. To gain access via hierarchy security on any entity, Manager or Supervisor should have at least user level read access on that entity
  7. If we wish to exclude any entities from Hierarchy security access, it can be done from Settings>Security>Hierarchy Security

HierarchySecurity.png

 

 

Read the rest of this entry

Changing parent BU removes security roles assigned to the users of that BU – Issue fixed in CRM 2015

There was a strange issue in CRM 2011 where the security roles of users part of a BU get removed when the BU’s parent BU is changed. This issue seems like fixed by Microsoft in CRM 2013 RU2 and we do not see that issue in CRM 2015 either.

 

If you are still using CRM 2011 and are affected with this issue, a work around would be to reassign the security roles through custom code or from UI after the parent BU change.

Through Code:

<pre>// Associate the user with the role.
        if (_roleId != Guid.Empty && _userId != Guid.Empty)
        {
            _serviceProxy.Associate(
                        "systemuser",
                        _userId,
                        new Relationship("systemuserroles_association"),
                        new EntityReferenceCollection() { new EntityReference(Role.EntityLogicalName, _roleId) });

            Console.WriteLine("Role is associated with the user.");
        }</pre>