Author: uk365guy

 Many companies considering Microsoft Dynamics CRM are weighing the options of installing Dynamics CRM On Premises or going with CRM Online. In this document we compare the two platforms, look at what is similar, and compare the differences.

Core Application FunctionalityThe core application functionality is at parity, with the same core application entities and extensibility features.ExtensibilityCustomizations developed in a supported way for CRM on premise can be moved to CRM Online (and vice versa), and plugins, workflows and any custom extension can be used in either Online or On Premises deployments. Any supported code will work in both CRM online and On Premises.MobilityCRM clients for phone, tablet, and Outlook (including offline) work exactly the same between CRM Online and CRM On Premises.
Integrations with other Microsoft platformsIntegration with other Microsoft platforms such as Sharepoint, Exchange, Lync, and Yammer work with both CRM On Premises as well as CRM OnlineIf you currently use Office 365 for Exchange or SharePoint, CRM Online will allow you to standardize user management and offer enhanced server side integration with SharePoint Online, Exchange Online, and PowerBI.Data Integration OptionsIntegration options are similar between CRM online and On Premises. Third party integration tools like Scribe Insight and SSIS with Kingswaysoft work with both CRM On Premises and CRM Online. Integration performance will vary based on the data loaded. Very large data integrations are typically faster with CRM On Premises if the integration server is close to the CRM server as latency is very low. CRM Online integration performance can be improved by optimizing the integration, using the bulk load API, or by reducing latency to the cloud by running the integration from a Microsoft Azure server. 

Capability	CRM Online	CRM On Premises
Exchange synchronization	CRM for Outlook, Email Router, or Server synchronization(if using Exchange online/O365)	CRM for Outlook, Email Router, or Server Synchronization(if using Exchange on premises)
SharePoint Integration	Server Side with SharePoint Online(if using Client-side Integration	Server Side with SharePoint
Inside View (Insights)	Included	Additional cost
Social Listening	Included	Additional cost
Workflows/dialogs	200	Unlimited
Custom Entities	300	Unlimited
SSRS Reporting	FetchXML, or T-SQL from a locally replicated reporting server	FetchXML or T-SQL
Power BI Reporting	Yes	No
Upgrade/Update Process	Office 365 admin approve the upgrade it is installed, update rollups applied automatically.	Upgrade and update rollups installed by your adminstrator
Direct server access	No	Yes
Phone App	Yes	Yes if environment externally facing via ADFS
Tablet App	Yes	Yes if environment externally facing via ADFS
Storage	Limited to the amount of CRM Online storage purchased	Limited to the amount of storage available on your server
Release cycle	Two releases per year. Spring release functionality exclusive to CRM Online, so  new functionality available online first	Fail release released to both CRM Online and On Premises, includes the functionality released in the spring release.
Migrating	CRM Online customers can migrate On Premises at any time.SQL database provided to client at scheduled time that can be imported to an On Premises deployment.	CRM On Premises customers can migrate to CRM Online and customization for entities can be imported, however, on premises database cannot be moved to Online data center, so a data migration is required.
Sandbox environments	CRM Online provides non production environments as part of your subscription that can be used for dev/test/UAT. The number of organisations received depends on the numbers of users.	Non production environment can be installed, depending on local server availability.

 

Hi there

Please find the some of the new features of the microsoft dynamics crm  2011/2013/2015/2016
as follows:

This below links for Microsoft dynamics crm 2016

http://www.powerobjects.com/2015/12/15/the-force-is-strong-with-this-version-top-new-features-in-microsoft-dynamics-crm-2016-online/

What is new for Administrators and Customizers in Microsoft Dynamics CRM 2016 and CRM online

https://technet.microsoft.com/library/dn531078(v=crm.8).aspx

What is new In Microsoft Dynamics CRM 2016

https://www.microsoft.com/en-us/dynamics/crm-customer-center/what-s-new.aspx

What is new for Developers in Microsoft Dynamics CRM 2016

https://technet.microsoft.com/en-us/library/gg309589.aspx

This below links for Microsoft dynamics crm 2015

http://www.powerobjects.com/2014/09/16/top-10-new-features-dynamics-crm-2015/

What is new for Microsoft Dynamics CRM ONLINE 2015 UPDATE 1

https://msdn.microsoft.com/en-us/library/gg309589(v=crm.7).aspx#BKMK_NewInSpring2015

This below links for Microsoft dynamics crm 2013

http://www.powerobjects.com/2013/09/06/top-10-new-features-of-crm-2013/

This below links for Microsoft dynamics crm 2011

http://www.enterpriseappstoday.com/crm/top-10-features-of-microsoft-dynamics-crm-2011.html

http://www.mareeba.co.uk/blog/2011/01/microsoft-dynamics-crm-2011-new-features.html

1. > Create 4 contact record. (A,B,C,D)
2. > 3(B,C,D) Contact record will be child of 1(A-Parent)
3. > When ever A-Parent information will be changed should be refelected to their respective child also. -plugin/Jscript
4. > Selection of parent lookup — Data wil be fetch through Jscript OData.
Description
———–
Optionset value -> Parent/Child

[ If parent is selected from parent/child field then parent field and parent section fields parentemail and parentphonenumber will be disabled]
[ if child is selected from parent/child field then parent field should be required field and the parent section fields parentemail and parentphonenumber should be
auto populated from parent record].

Create new entity Donation
create fields
————-
parent/child = optionset = parent, child(business required field)
parent = lookup to itself
emailaddress = text field
phonenumber = phonenumber
gender = optionset= male/female
companyname = text field
designation = text field
city = text field
country = lookup to country entity//(in the country entity only add country field)

CREATE NEW SECTION CALLED PARENT SECTION LABEL(TWO COLUMN)
Fields
—–
parentemail = text field
parentphonenumber = text field

======================================================================
Javascript  is as follows:

function FormOnLoad() {
    /*For Type
    0 -Undefined
    c  1- Create
    u 2-Update
    r 3-ReadOnly
    d 4 -Disabled
    */
    var type = Xrm.Page.ui.getFormType();
    Xrm.Page.getControl(“new_parentemail”).setDisabled(true);
    Xrm.Page.getControl(“new_parentphonenumber”).setDisabled(true);
    if (type == 1) {//Create Mode
        //TODO : by default optionset value will be parent and parent lookup should be disabled.
        var optionSet = Xrm.Page.data.entity.attributes.get(“new_parentchildoptionset”);
        optionSet.setValue(100000000);
        Xrm.Page.getControl(“new_parent”).setDisabled(true);

    } else {
        var parentChildOptionSet = Xrm.Page.data.entity.attributes.get(“new_parentchildoptionset”);
        if (parentChildOptionSet != null) {
            var optionsetvalue = parentChildOptionSet.getValue();
            // this for parent
            if (optionsetvalue == 100000000) {
                Xrm.Page.getAttribute(“new_parent”).setRequiredLevel(“none”);
                Xrm.Page.getControl(“new_parent”).setDisabled(true);
             
            } else if (optionsetvalue == 100000001) {
                Xrm.Page.getControl(“new_parent”).setDisabled(false);
                //Setting the required filed
                Xrm.Page.getAttribute(“new_parent”).setRequiredLevel(“required”);
            }
        }
    }

}
function OnChange_ParentChildOptionSet() {
   
    var optionsetvalues = Xrm.Page.data.entity.attributes.get(“new_parentchildoptionset”);
    var optionsetvalue = optionsetvalues.getValue();
    // this for parent
    if (optionsetvalue == 100000000) {
        Xrm.Page.getAttribute(“new_parent”).setRequiredLevel(“none”);

        Xrm.Page.getControl(“new_parent”).setDisabled(true);

    } else if (optionsetvalue == 100000001) {//Child
        Xrm.Page.getControl(“new_parent”).setDisabled(false);
        Xrm.Page.getAttribute(“new_parent”).setRequiredLevel(“required”);
    }

}
function OnChange_ParentLookup() {
    var parentlookup = Xrm.Page.getAttribute(“new_parent”).getValue();
    if (parentlookup != null) {
        var lookupId = parentlookup[0].id;
        var CrmServerUrl;
        if (typeof GetGlobalContext != “undefined”) {
            CrmServerUrl = GetGlobalContext().getClientUrl();
        } else {
            if (typeof Xrm != “undefined”) {
                CrmServerUrl = Xrm.Page.context.getClientUrl();
            } else {
                alert(“Context is not available.”);
            }
        }
        if (CrmServerUrl.match(//$/)) {
            CrmServerUrl = CrmServerUrl.substring(0, Crm.length – 1);
        }

        //REST SERVICE WITH ODATA.
        var oDataPath = CrmServerUrl + “/XRMServices/2011/OrganizationData.svc”;
        var fetchData = new XMLHttpRequest();
        var Odata = oDataPath + “/new_donationSet?$select=new_phonenumber,EmailAddress&$filter=new_donationId eq (guid'” + lookupId + “‘)”;
        fetchData.open(“GET”, Odata, false);
        fetchData.setRequestHeader(“Accept”, “application/json”);
        fetchData.setRequestHeader(“Content-Type”, “application/json; charset=utf-8”);
        fetchData.onreadystatechange = function () { retrieveParentDetails(this); };
        fetchData.send();

    }
}
retrieveParentDetails = function (fetchData) {
    if (fetchData.readyState == 4) {
     
        var fetchD = this.parent.JSON.parse(fetchData.responseText).d;
       
        if (fetchD.results.length > 0) {
            var phoneNumber = fetchD.results[0].new_phonenumber;
            var email = fetchD.results[0].EmailAddress;
            Xrm.Page.getAttribute(“new_parentphonenumber”).setValue(phoneNumber);
            Xrm.Page.getAttribute(“new_parentemail”).setValue(email);
        }
    }
}