To Top
Invest in a good integration tool

SALESFORCE INTEGRATION PATTERNS AND BEST PRACTICES FOR SALESFORCE USERS

Publish date:

SALESFORCE INTEGRATION PATTERNS AND BEST PRACTICES FOR SALESFORCE USERS

In this blog post, we shall examine in brief the various Salesforce Integration Patterns. This is an important topic and source of much discussion in the tech world. With Salesforce gaining ground, it is imperative to be knowledgeable on various aspects of Salesforce integration as knowledge is the key to success.  

We look at some best practices for Salesforce integration that will help to ensure a smooth transition: 

Verify migration of data – Data is the treasury in each organisation. The future of each company lies in clean and usable data. However, we need to be clear in which data should be migrated to salesforce and which should not. The two should be segregated. 

Source data – The integration process involves collaboration with team members who know the source of data and where to get it from. This involves interacting with many team members and requires the vendor team to obtain a good knowledge of the details behind each element desired. 

Integration schedule – Real-time and two-way integration is the ideal result of the integration process. Some issues may prevent this such as lack of finances or the company has multiple SIS systems, so some data is available only once a day. Therefore, most companies start with a daily batch process 

Salesforce data model – You should go in for a salesforce data model that is the right requirement for your company. 

Help Text – 255 characters are available to help users understand the context behind every available data for each given field. 

External IDs – External IDs permit parking of a key on a salesforce record that can be used to update from an external source. 

Use team’s expertise – This is the time to leverage the skill set of your employees or team members.  Based on the skills at hand, decide where data manipulation will take place during integration.  It could be in the source system database, in an ETL tool, or with Workflow and Apex in Salesforce. 

A tool to manage the process – There are a variety of integration tools in the market which provide a salesforce connector. It is ideal to invest in one. These tools identify data issues and send out emails/alerts to let the process owners know that there is an issue with the data. 

Adding additional data - With a successful integration, you may start feeding in additional data to the process as and when required. 

The five types of integration patterns in Salesforce are:  

  • Request & reply – Salesforce solicits a process on a system, waits for its completion, and then tracks state based on the response from the system. The options for request & reply include:  

    • External Services: Point & click-based integration from Lightning Flow.  

    • LWC or Visualforce calling external system: Salesforce enables you to consume WSDL and generate proxy classes  

    • Trigger: We can make a callout to the external system on data changes via a trigger.  

    • Batch Apex invoking external services: We can make a callout to an outside system using Batch Apex.

  • Fire & forget - Salesforce solicits a process on a system but does not wait for it to run its course. Here the remote process gets and acknowledges the request followed by giving control to Salesforce. This can be done in the following ways:  

    • Process-driven platform events  

    • Customization-driven platform events  

    • Workflow-driven outbound message  

    • Apex based Callouts  

  • Batch data synchronization – Data in the lightning platform is designed or refreshed to reflect updates from an outside system, and when changes from the lightning platform are sent to an outside system. Updates happen in either direction in a batch manner.  

    • Data Capture: Salesforce publishes change events, which represents amendments on records  

    • Manual Remote Calls: Salesforce or the out

    • Using ETL Tool: This tool connects to systems, obtain data, change in the desired target format and uploads using Bulk API or SOAP API  side system can call each other every time data is modified.   

  • Remote Call in - The data in the lightning platform is made, updated or deleted by a remote system.  

    • SOAP & Rest API  

    • Apex based APIs  

  • Data Virtualisation – Salesforce accesses outside data in real-time. This eliminates the need to persist data in Salesforce and then accommodate the data between Salesforce and the outside system.  

Codleo consulting is the best Salesforce Integration Partner for your salesforce integration services requirement. Contact us as your Salesforce Integration Partner today for your Salesforce integration services requirements.

About the Author

author
Mohit Sharma

Mohit is Practice Lead, 4x Certified Salesforce Consultant, Salesforce trainer, blogger, writer, and full-time husband. With over 8 years of experience implementing Salesforce, and an obsession for innovation, ready to tackle any new project that comes his way.

Leave a Comment

FEEDBACK