MDM Flashcards
The management of the company has decided to switch from a legacy CRM to Salesforce. The company will follow a phased implementation plan for the Salesforce deployment. Until all the functionality has been deployed, the two systems should be kept in place and the data should be kept in sync between the different systems used by the company.A master data management (MDM) solution is being considered for data synchronization and to define a single point of reference for all the important master data, which also includes reference data. The IT manager would prefer a non-intrusive approach for the implementation so that the data in the source systems are not touched.
Furthermore, the golden record or the single version of truth should be stored in the central hub for reporting and reference. The data architect needs to share information about different implementation styles, suggest an appropriate style for the MDM implementation, and provide any considerations related to data synchronization between MDM and the different systems used by the company.
The Registry style is typically used when there are various source systems and there is a need to identify duplicates by running cleansing and matching algorithms on data from the source systems. Unique global identifiers are assigned to matched records to help identify a single version of the truth. Although this is a non-intrusive approach since the source systems remain unchanged and changes to the master data continue to be made through existing source systems, it does not utilize a central hub. This style can be utilized when a company has multiple low control and autonomous systems, and there is a need for distributed governance by those remote systems.
Salesforce Connect
A global company in the electronics industry has been operating for more than a decade already and has been using the different Salesforce products such as Sales Cloud and Service Cloud which significantly helped them in achieving their success milestones throughout the years.With millions of old records in the org, they want to archive data to free up storage. However, they will need to access these records in the future for referencing and featuring in case studies, conducting business intelligence analysis, and other purposes. The company still has an active SAP environment which was one of their primary tools before.
Salesforce Connect uses external data sources which enable an org to access data in a remote system. This functionality is made possible with the use of adapters and one of the types of adapters Salesforce Connect supports is OData adapters. SAP is capable of exposing data via OData producers.
As a solution, data that needs to be archived can be migrated to the company’s SAP database. Then, Salesforce Connect can be used to connect to the SAP instance and allow org users to perform standard operations on the archived data such as search, relate them to other objects in the org, and even create certain reports on them.
- Salesforce Connect
- External data source
- OData adaptor
Salesforce Connect
A thriving travel agency uses Salesforce to manage records of their customers, deals & promotions, travel destination recommendations, and perform sales-related activities in their daily business processes.
They would like to be able to work with an external service that returns a list of available flights from different partner airlines just by conveniently providing the preferred flight date and conditions such as number of passengers, price range, and other settings.
Providing the capability as a SOAP service, this external system also enables the requesting client to purchase selected flights through it to serve as a digital one-stop shop.
In this scenario, a Request and Reply integration can be implemented. Since the external system provides its services over SOAP, a custom user interface in Salesforce, such a custom Lightning web component, can be developed where AuraEnabled Apex controllers make use of the available SOAP API that Salesforce offers.
When an org user populates and submits a form that requests for available flights, the Lightning component synchronously forwards this request to the external system. When Salesforce receives a reply, the results can then be displayed for example in a Lightning datatable.
- Request and Reply
- SOAP
- LWC + Aura enabled Apex
Salesforce Connect
A retail company runs an e-commerce website which allows customers to browse its extensive product catalog, purchase items, and have orders delivered right to their doorsteps. The website, which is built on the Heroku platform and uses a Postgres SQL database, processes these transactions at an increasingly daily rate.
To augment its customer service capabilities as well as enhance its sales and marketing strategies and efforts, it has recently started using Salesforce.
The company is looking for an integrated solution that would enable org users from the customer service team to access website data such as sales and orders for referencing and other uses to become more efficient in handling customer enquiries, complaints, and feedback.
Heroku Connect can be added to the application in the Heroku platform to share and synchronize data between the Salesforce database and Postgres database. In a typical setup, Salesforce will have an exact copy of the mapped database tables in Heroku. Then, with bidirectional synchronization enabled, changes made to records in Salesforce can be synced to Heroku if necessary, and changes made in Heroku can be synced back to Salesforce.
However, if Heroku External Objects is used, data will reside in the Postgres database only. Then, Salesforce Connect is required in order to access data in Heroku from the Salesforce org. In this type of setup, data is accessed on demand real-time and no synchronization process is needed as no records are copied or moved into the Salesforce org.
- Heroku Connect
- bidirectional synchronization
- Salesforce Connect
- Heroku External objects
Salesforce Connect
A global company that sells furniture has been using a homegrown order management system to manage sales orders and related invoices. But due to the large volume of data and the age of the system, accessing or updating a sales order or invoice takes a long time. That’s why the company would like to switch to an ERP system for managing orders and invoices.
However, until the sales users have been properly trained to use the new system, the sales director would like them to use Salesforce to search, view and modify orders and invoices stored in the order management system. Orders and invoices are related via a lookup relationship, which must be maintained in Salesforce. However, there is already an object named ‘Invoice’ in Salesforce, which should be considered. Furthermore, developers who have integrated with the order management system in the past have experienced connection timeout issues, which is another aspect to consider.
Salesforce Connect can be set up to allow Salesforce users to search, view and modify orders and invoices. An external data source can be created in Salesforce for the order management system. External objects that represent orders and invoices can be created automatically by syncing the external data source. ‘Writable External Objects’ can be enabled for the external data source.The data does not get stored in Salesforce - only in the external data source.To ensure that there is no naming conflict during external data source sync, the external object name can be edited inline. To avoid a connection timeout issue, the sync operation can be run asynchronously as a background job. Syncing the orders and invoices would create an external lookup relationship field between the mapped external objects in Salesforce automatically.
Salesforce connect
Writable External Objects
Inline Editing
Async run in the backgroung to avoid timeouts
External lookup relationship
