Archive

Archive for the ‘Salesforce’ Category

How to get started with Salesforce development

November 14, 2014 Leave a comment

Setting up Developer Environment

  1. Register developer account at https://developer.salesforce.com/
  2. You can login your org from http://www.salesforce.com/
  3. Install Salesforce IDE for eclipse https://developer.salesforce.com/page/Force.com_IDE_Installation

Understand the different Salesforce Environment

Developer ,Sandbox, Production

Deployment

 Deployment by Changeset Best practice

CI and team development with Salesforce

How To Use Git, GitHub and the Force.com IDE with Open Source Labs Apps

Using Force.com with Subversion for Team Development

http://www.soliantconsulting.com/blog/2013/03/salesforcecomforcecom-team-development

http://salesforce.stackexchange.com/questions/18881/how-to-use-git-on-multi-dev-environment

Deployment is a one-way transaction

There is no easy way to roll back changes deployed in Production. As documented here . It is another reason we should look at the next support level. A change set is deployed in a single transaction. If the deployment is unable to complete for any reason, the entire transaction is rolled back. After a deployment completes successfully, all changes are committed to your organization and the deployment can’t be rolled back.

Salesforce known issues

https://success.salesforce.com/issues_index

Salesforce Books

  1. Salesforce workbook
  2. Cheat Sheets
  3. Documentation

Videos Training

  1. Search for Dreamforce from YouTube , Dreamforce is the salesforce conference , like the Teched in Microsoft.
  2. Pluralsight offer some good developer training
  3. cbtnuggets offers Power user training
  4. Beginner Tutorials
  5. http://www.forceprepare.com/

Blogs

http://www.shellblack.com/blog/

http://blog.jeffdouglas.com/

Documentations from Salesforce

Considerations for Relationships

Salesforce Limit

Understanding Encrypted Custom Fields

Encrypted Field Limits

Advertisements

Salesforce deployment best practice?

October 1, 2014 1 comment

I am very new to Salesforce and as you can see from my blog, I am .Net developer and more specifically a SharePoint developer. In salesforce , there is no clear strategy for release management and I am asking the wider Salesforce community to help me to see if the proposed release plan is OK.

The current deployment model we use are multiple Sandbox environments and changeset to deploy change from Dev >> Test>>Preprod>>Prod . Here are the challenges I understand so far in Salesforce deployment.

  1. You cannot rollback after a changeset is successfully deployed
  2. Creating changeset is very manual

To address the first issue (You cannot rollback after a changeset is successfully deployed):

  1. Backup the data by scheduling a weekly data export (my question would be , how we can use the data export to restore the data)
  2. Backup the apex code (trigger, visual force…), we can use eclipse to deploy these changes so that the apex code can be rolled back.
  3. Document all the schema changes(custom object, custom fields, custom labels, tabs …) , if we do need rolled back we can manually delete all those changes..

To address second issue (Creating changeset is very manual)

We are looking at using Salesforce IDE or Salesforce migration tool to deploy the changes from environment to environment.

Reference:

Deploy Force.com Applications to Production Faster,

Using the Force.com IDE to Deploy Apex

Salesforce deployment guideline using Sandbox

July 10, 2014 Leave a comment
  1. Create Deployment connection
  2. Enable the inbound change set settings on the destination Environment you would like to deploy the solution to.
  3. Enable the outbound change set settings on the source Environment where you package your application.
  4. The best practice is to Package everything in the changeset and salesforce will only deploy the change into your destination environment. If you only package the change, you could miss some of the changes.
  5. You can clone the change set on the source destination however the initial packaging takes some time as you need to go through everything and select the components manually.
  6. After the change set is packaged, you need to upload the chagneset so that destination environment can see the change set in its incoming change set list.
  7. Click Validate the change set before deployment.

References:

Development Lifecycle Guide

Change Sets Best Practices