SFDC – Logistics – Orgs Integration – Success Story

Client Overview

The client is a US based Logistic and Transloading service provider, focused on providing efficient supply chain solutions.

Client’s supply chain network involved fleet management of newly built covered hopper cars, extensive railcar monitoring & consulting services, along with logistic network for car diversions and/ or storage, automated facilities for silo storage, quick railcar offloading and truck loading as well as testing of products.

Business Challenge

Client’s Silo management business required transferring of Silo to Railcars and Railcars to Trucks. The client was entering Silo loading and offloading transaction data using Silo Terminal Application, which in turn saved the data into the Salesforce org. The client was using multiple Salesforce orgs for multiple customers. This solution approach was not scalable, as the customers were constantly increasing. It made Salesforce org maintainability cumbersome in terms of the security, data, configuration etc. Additionally, client was facing huge cost overheads due to the procurement of a new Salesforce org for every new customer. The monthly data backup process was also problematic as the same backup process needed to be executed separately for every Salesforce org, which sometimes raised data integrity issues.

To overcome these challenges, the client wanted to enhance the existing Salesforce org to become useful for multiple customers and desired for data privacy between the customers. The users associated with a particular customer should able to view their respective data only and other customers’ data should be invisible to them.

The objectives of the project were as listed below:

  • Consolidation of all Salesforce orgs into a single Salesforce org to make a single instance of Salesforce for managing all customer data

  • Manage data privacy of every customer

  • Change of configuration and security model on the final Salesforce org for the work consolidation

  • Data Migration required to move all customer data from various Salesforce orgs to the final Salesforce org

Technical Requirements

  • Apex Data Loader

Solution Strategy

  • Eternus Solutions reviewed the business objectives and worked with the client to develop a single Salesforce org for managing all customer data.

  • Eternus Solutions team identified the main Salesforce org where consolidation would be possible. The team analyzed all Salesforce orgs to map the common objects and fields from the source orgs to the destination org. To maintain data privacy between customers’, different profiles, apps, page layout and record types were configured. It enabled the users to view and enter data associated with a particular customer into his respective app.

  • Eternus Solutions team exported data from all source Salesforce orgs and imported them into the destination Salesforce org using data loader. To summarize data of each customer distinctly, separate custom reports and dashboards were configured for each customer app.

Solution Components

  • Use of profiles, roles, sharing rules and organization wide defaults for management of user permissions and access rights

  • Use of page layouts to define visibility and editable fields for the profiles

  • Use of record types to display different page layouts for each profile

  • Use of data loader to export data from the source orgs and import data into the destination org

Development Methodology

  • Development and testing on the Production Org

  • Extensive use of custom profiles, record types, custom apps, sharing rules, organization wide defaults and page layouts

  • Development using SFDC standards and best practices

  • Tracking of development on mail

Share This Case Study