Archives / 2015 / September
  • Microsoft Dynamic CRM Managed Vs. Unmanaged Solutions

    Microsoft Dynamic CRM supports two types of solutions:

    • Managed solution
    • Unmanaged solution.

    Managed Solution:

    A managed solution is a completed solution in which the solution is prevented from being modified in the environment to which it is imported. A managed solution is intended to be distributed and installed.

    • Possible to set granular levels of rights to alter elements of the solution such as create views, change field properties, add fields etc.

    • Solution cannot be exported.

    • Easier administration with new versions. Any changes including field removal will be rendered

    • If the solution is removed all the customizations pertaining to that solution will be removed and there will be a Risk of data loss.

    Once the managed solution is imported following steps takes place:

    • User cannot add or remove the components in a managed solution.
    • User cannot Export a managed solution.
    • By deleting the managed solution all the components in the solutions will also be uninstalled.
    • Managed solution can be overridden by another new version of managed solution.

    Unmanaged Solution:

    Unmanaged solution allows the solution to be modified after it is imported. Unmanaged solution is still under development stage and it is not intended to be distributed or installed.

    • All the elements or components in the solution can be customized without any restriction.
    • An unmanaged solution can be exported.
    • When the unmanaged solution is completed and ready to distribute it, export it and package it as a managed solution.

    · Unmanaged solution files can be transported from one environment to the other.

    • Entities, Fields, web resources can be removed manually.

    The solution acts as a container for the components. If user deletes the solution the components still exist in the default solution.

    When a solution is unmanaged, the following steps can takes places:

    • Components can be added and removed.
    • Components can be deleted that allow for deletion.
    • Can Export and Import the unmanaged solution.
    • Unmanaged Solution can be exported as a managed solution once the changes are done.
  • Calculated Fields in MS CRM 2015

    Calculated fields will now be able to calculate the difference between two date fields in minutes, hours, days, weeks, months, or years. Calculated fields are something that has always been requested on projects and usually these have been completed with workflows or using Business Rules. Fields can be added to CRM and set to automatically calculate using Excel-like formulae.

    How to Set Up Calculated Fields:

    • To set up a new calculated field, create the field, as normal, and click on the Field Type drop down. Changing this from Simple to Calculated makes the field a calculated field.
    • Create a condition for No of days that has to be met for the field to be calculated. For Example if the condition is the difference in days between the end date and start date when both fields are populated. In order to satisfy this condition first create start date and End date fields with Date and Time Data Type  and No of days field with field type as “Calculated”.



    • Select ‘Edit’ next to the Field Type to set up the calculation logic



    • After clicking on edit a window appears as below



    • Click on “Add condition” and then start giving the condition for No of days to be calculated
    • Initially give the condition as Start Date for field by selecting the related entity under Entity  to that field.



    • And give the condition for the End Date by selecting the related entity.



    • The next section is the 'Action' for the condition and then click on tick mark.




    • Finally click on save and close.
    • In order to check the calculated field created Navigate to sales and select the particular entity in which the field is created



    • Click on the statistics entity and give the details of start date and end date and save it .The difference between both the fields for No of Days will be populated automatically



  • Hierarchical Security Models in MS CRM 2015

    Hierarchy SM introduced in MSCRM 2015

    The hierarchy security model is an extension to the existing Microsoft Dynamics CRM security models that use business units, security roles, sharing, and teams. It can be used in conjunction with all other existing security models. This new change will make it possible for managers to see records for the people under them.

    This model leads a direct manager of a user to Read, Update, Append, Append To and only Read privileges to the manager of a direct manager of subordinate activities.

    Hierarchy security model has two models:

    • Manager hierarchy
    • Position hierarchy

    Navigate to Settings -> Security and select Hierarchy security


    • Choose Hierarchy security and enable hierarchy modeling
    • Choose manager hierarchy or custom position hierarchy.

    Manager Hierarchy:

    With the Manager hierarchy, a manager must be within the same business unit as the report, or in the parent business unit of the report’s business unit, to have access to the report’s data.

    Custom Position Hierarchy:

    The Position hierarchy allows data access across business units. A user doesn’t have to be an actual manager of another user to access user’s data. As an administrator, you will define various job positions in the organization and arrange them in the Position hierarchy.

    Hierarchy Depth:

    • The amount of data accessible can be limited with the depth. Depth is used to limit how many levels deep a manager has Read-only access to the data of their reports.

    In hierarchy security all the system entitles are enabled and end user can exclude the entities that don’t want to be included in the hierarchy security.


    After selecting Manager Hierarchy a user record can be viewed by opening the users list and then select view hierarchy


    This window shows the relationship of the manager with the other users in the same business unit.

    In the below scenario a user1 can have direct access to user2 i.e (can have read, write, append, append to) permissions.


    In the below scenario user2 can have direct access to user3, but user1 can only have a read permission to this user3.


    Navigate back to the hierarchy security and enable custom position hierarchy.

    To create a Position hierarchy:

    • Go to setting - > security
    • Enable custom position hierarchy.
    • Choose Positions

    For each position, provide the name of the position, the parent of the position. Add users to this position by using the lookup field. Below is the example of Position hierarchy with the active positions.


    Select any position under active positions and click on view hierarchy.



Please Wait