Month: May 2016

Cross Object Formulas in Salesforce

Cross Object Formulas in Salesforce

Cross Object Formulas in Salesforce refers to fields in records that are related to the current record that the formula is being applied to Example:-. the formula might apply to a Contact record, but in that formula you might want to refer to the related Account record. has made this very simple and the feature is aptly named Cross Object Formulas.

Note:- To retrieve the data of child records from their parents record the syntax for these references is natural and precise. Consider the situation where you need to create a formula for a Contact record, but you need to refer to the related Account’s parent Account’s name. In this case the syntax would be i.e. you access the field value by using the related field names (separated by periods) until you arrive at the object field in question. For custom objects the syntax is slightly different e.g. if the formula applies to a custom object and needs to interrogate the parent object’s name field through the Parent__c relationship field, the syntax would be

Where can we use Cross Object Formula in Salesforce?

Cross Object Formulas can be used in a number of areas within the platform as previously mentioned, and depending on their context can be used to achieve different types of results.

What is a Formula Field in Salesforce?

Formula Field in Salesforce are read-only fields with values defined by the underlying formula. Data in these fields are not persisted but is calculated on the fly when the field is accessed. Creating formula fields can be done from the same area as the other field types.

  • Using formula functions you implicitly have access to some “sub” field- types including hyperlinks and images.
  • You are free to use any combination of formula component in formula fields as long as the resultant value is of the pre-determined type.

Never use a formula field as an indexing or filtering value. If you need a field value to be dynamically calculated but know that it will be used to filter data through API calls or in the WHERE clause of any SOQL statement, consider using static fields in combination with workflows instead. The reason here is that the calculation of formulas can be especially taxing “under the hood” to the platform in these conditions and will result in a performance loss.

Change Sets In Salesforce – Overview

What are Change Sets in Salesforce?

Change sets in Salesforce are the newest method for deploying code and components and provides some enhanced functionality. Changes sets in Salesforce use packages in the background but provide the ability to move code from not only sandbox to production, but from sandbox to sandbox and production to sandbox.

While deployment with the, Migration Tool and the IDE are tasks typically performed by developers, change sets are focused more for administrators. For larger companies this allows multiple developers to create change set that are deployed by administrators who may have more intimate knowledge of their entire landscape. Before deploying change sets in Salesforce, administrators must setup trusted deployment connections between their Organisations.

  • Deployment connections can’t be created between arbitrary Orgs.
  • By default a deployment connection is created between all Orgs affiliated with a production Org (e.g., sandboxes).
  • Connections are created between each sandbox and between each sandbox and production Org.
  • A deployment connection alone doesn’t enable change sets to be sent between Orgs.
  • Each Org must be authorized to send and receive change sets.
  • This added level of security enforces code promotion paths and keeps an Org’s metadata from being Org’s metadata from being overwritten by mistake.

Change sets in Salesforce

When sending changes from your current Organisations to another Organisation, we must create an outbound change sets in salesforce. The process to create and deploy a change set is relatively straightforward. Firstly we must create a new change sets in Salesforce and then walk through a series of screens adding the component that you want to deploy. Once we Upload the change set, the receiving Organisation sees it as an inbound change set and can accept and deploy it with a few clicks. A change set is deployed as a single transaction. If the deployment fails for any reason, the entire change set is rolled back. After a deployment completes successfully, all changes in the set are committed to your Org and the modifications cannot be rolled back.