365 Wisdom Blogs

Continuous Integration (Build automation) for salesforce.com using GitHub repository: Step by Step by Jenkins Setup I did a small POC for Jenkins setup to automate the build deployment (Continuous Integration) of SFDC and GitHub as repository on cloud.  I thought to share my experience. To start with let’s first understand the basics and approach I took to achieve this. Following are the  major components are involved to make it happen. These are not software requirement. Software requirements are defined later in this article. 1.                   Salesforce instance – Source e.g.: Dev Sand Box where the configuration and customization has been done. 2.                   Eclipse with force.com IDE: This used to pull the desired code and components to be deployed at other Salesforce.com instance. 3.                   GitHub repository as source control 4.                   Jenkins : It control the deployment 5.                   Salesforce-Ant build tool

While comparing between SFDC & Dynamics CRM, like other is Pricing is a very critical decision maker with other features & some time. Licensing price comparison with respective edition features:   Since November 2013, Unlimited Edition is no longer available for purchase. Existing Unlimited Edition customers can continue to renew Unlimited Edition, purchase additional licenses, or upgrade to Performance Edition, which includes all Unlimited Edition functionality plus Data.com, Work.com, Identity, Live Agent, Salesforce Knowledge, and additional sandbox functionality. Unlimited Edition customers can choose to upgrade to Performance Edition or continue to use Unlimited Edition, which will continue to receive enhancements and innovations during salesforce.com’s regular upgrade cycles. Data Storage: Differences in storage are important to note as well. Microsoft Dynamics CRM Online provides 5 GB of storage upfront compared to the 2 GB offered by Salesforce

As promised in my last article (Part-1) here is the next version. You can find part-1 down below this page. Reports and Dashboards Microsoft had a pre-developed reporting engine within SQL Server called SQL Server Reporting Services (SSRS). Therefore, they made an understandable decision to use SSRS as the CRM reporting engine rather than creating CRM-specific. To utilize SQL and SSRS with in CRM, Microsoft built the integration between the CRM application and the SSRS. On the other hand, in absence of its own reporting engine Salesforce built its reporting engine from scratch and then leveraged this creation.  Salesforce reports don’t offer One-Click drill down. Salesforce reports has a lag of 30-60 minutes There were 25 types of pre-build reports are provided by Dynamics CRM. Simple to normal reports can be created by native report Wizard provided with in CRM. The complex reports can be created using SSRS and then it can be imported with in CRM. Microsoft CRM claims almost

Salesforce and Microsoft Dynamics CRM are currently the two leading CRM systems in the market. Many people spend a lot of time trying to decide which of these two CRM solutions have the edge & what should we choose as an organization. We have seen Salesforce as CRm market leader and now Dynamics CRM is giving neck to neck competition. In this post, I am trying to summarize all the aspects of MS CRM and Salesforce for different stakeholders & I believe it would give better comparative knowledge. Implementers, Administrators, Business Analysts, Technical developers as well as end users have would get sufficient insight with deep comparisons. CRM User Interface and Navigation User interface of Microsoft CRM older version were based windows designing sense. Microsoft Dynamics CRM 2011 updated with the new ribbon interface just like office 2010 interface within the browser in order to give users a common experience across familiar Windows products and CRM. In 2013 Microsoft d