{"id":1802,"date":"2024-09-09T23:00:23","date_gmt":"2024-09-10T06:00:23","guid":{"rendered":"https:\/\/salesforcechronicles.com\/?p=1802"},"modified":"2024-09-10T19:04:18","modified_gmt":"2024-09-11T02:04:18","slug":"salesforce-data-cloud-data-mapping-best-practices","status":"publish","type":"post","link":"https:\/\/salesforcechronicles.com\/?p=1802","title":{"rendered":"Salesforce Data Cloud: Data Mapping &amp; Best Practices"},"content":{"rendered":"\n<figure class=\"wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<iframe loading=\"lazy\" title=\"Data Cloud Modelling and Best Practices\" width=\"726\" height=\"408\" src=\"https:\/\/www.youtube.com\/embed\/6ThgSCOMNAI?feature=oembed\" loading=\"lazy\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe>\n<\/div><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><\/h3>\n\n\n\n<p>In this post, we continue our deep dive into Salesforce Data Cloud, focusing on <strong>data mapping<\/strong> and the key steps and best practices to ensure seamless data integration within the platform.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>What is Data Mapping in Salesforce Data Cloud?<\/strong><\/h3>\n\n\n\n<p>When you ingest data into the Salesforce Data Cloud, it doesn\u2019t automatically become useful. The raw data must first be mapped to relevant <strong>Data Model Objects (DMOs)<\/strong> to ensure it\u2019s organised and accessible. Salesforce uses the <strong>Customer 360 Data Model<\/strong> to maintain consistency across the system. This model is divided into various subject areas (e.g., party, sales order), each with specific objects and attributes.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Types of Data Model Objects (DMOs)<\/strong><\/h3>\n\n\n\n<p>Before diving into the mapping process, it\u2019s important to understand the two types of DMOs available:<\/p>\n\n\n\n<p><strong>Standard Data Model Objects<\/strong>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>These are predefined objects such as contact, account, and case.<\/li>\n\n\n\n<li>Each standard object comes with commonly used fields that are ready for use.<\/li>\n\n\n\n<li>You can extend these objects by creating additional custom fields if necessary.<\/li>\n<\/ul>\n\n\n\n<p><strong>Custom Data Model Object<\/strong>s:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>If your business needs go beyond what the standard models offer, you can create custom DMOs from scratch.<\/li>\n\n\n\n<li>Custom DMOs allow you to define specific fields and relationships to meet your unique requirements.<\/li>\n<\/ul>\n\n\n\n<p><strong>Steps for Data Mapping in Salesforce Data Cloud<\/strong><\/p>\n\n\n\n<p>Let\u2019s walk through the data mapping process using an example from our fictional company, Techron Group:<\/p>\n\n\n\n<p>1. Accessing the Data Stream<\/p>\n\n\n\n<p>Log into your Salesforce org and navigate to the Data Stream tab. Here, you\u2019ll find a list of the data streams created to bring data into the Data Cloud.<\/p>\n\n\n<div class=\"wp-block-image is-style-rounded\">\n<figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"904\" height=\"464\" src=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image.png\" loading=\"lazy\" alt=\"\" class=\"wp-image-1809\" srcset=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image.png 904w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-300x154.png 300w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-768x394.png 768w\" sizes=\"auto, (max-width: 904px) 100vw, 904px\" \/><\/figure>\n<\/div>\n\n\n<p>2. Initiating the Mapping Process<\/p>\n\n\n\n<p>Select the relevant data stream (e.g., order data stream) and locate the data mapping section on the right-hand side.Click Start to begin the mapping process.<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"904\" height=\"462\" src=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-1.png\" loading=\"lazy\" alt=\"\" class=\"wp-image-1810\" srcset=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-1.png 904w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-1-300x153.png 300w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-1-768x392.png 768w\" sizes=\"auto, (max-width: 904px) 100vw, 904px\" \/><\/figure>\n<\/div>\n\n\n<p>3. Mapping Data Lake Objects (DLOs) to Data Model Objects (DMOs)<\/p>\n\n\n\n<p>In the mapping interface, you\u2019ll see Data Lake Object (DLO) fields on the left and Data Model Objects (DMOs) on the right.<\/p>\n\n\n\n<p>Click on Select Objects to view both standard and custom DMOs.Choose the appropriate DMO (e.g., Sales Order DMO) and map the fields from your DLO to the corresponding fields in the DMO.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"904\" height=\"468\" src=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-2.png\" loading=\"lazy\" alt=\"\" class=\"wp-image-1811\" srcset=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-2.png 904w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-2-300x155.png 300w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-2-768x398.png 768w\" sizes=\"auto, (max-width: 904px) 100vw, 904px\" \/><\/figure>\n\n\n\n<p>4. Creating Custom Fields<\/p>\n\n\n\n<p>If a standard DMO lacks a field you need, you can create a custom field.Click Add New Field, provide a name, and select the appropriate data type (e.g., text, number).Map the newly created custom field to the corresponding DLO field.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"904\" height=\"460\" src=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-3.png\" loading=\"lazy\" alt=\"\" class=\"wp-image-1812\" srcset=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-3.png 904w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-3-300x153.png 300w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-3-768x391.png 768w\" sizes=\"auto, (max-width: 904px) 100vw, 904px\" \/><\/figure>\n\n\n\n<p>5. Saving and Validating Mappings<\/p>\n\n\n\n<p>After completing your mappings, make sure to save them.You can review or modify the mappings later by revisiting the Data Stream tab.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"904\" height=\"460\" src=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-4.png\" loading=\"lazy\" alt=\"\" class=\"wp-image-1813\" srcset=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-4.png 904w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-4-300x153.png 300w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-4-768x391.png 768w\" sizes=\"auto, (max-width: 904px) 100vw, 904px\" \/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Best Practices for Data Mapping<\/strong><\/h3>\n\n\n\n<p>To ensure efficient data mapping, here are some best practices:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Create a Data Dictionary<\/li>\n\n\n\n<li>Extend the Standard Data Model<\/li>\n\n\n\n<li>Visualize Data Relationships<\/li>\n\n\n\n<li>Check Mapping Compatibility<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\"><\/h3>\n","protected":false},"excerpt":{"rendered":"<p>In this post, we continue our deep dive into Salesforce Data Cloud, focusing on data mapping and the key steps and best practices to ensure&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"inline_featured_image":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1,26],"tags":[],"class_list":["post-1802","post","type-post","status-publish","format-standard","hentry","category-blog","category-data-cloud"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/salesforcechronicles.com\/index.php?rest_route=\/wp\/v2\/posts\/1802","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/salesforcechronicles.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/salesforcechronicles.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/salesforcechronicles.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/salesforcechronicles.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1802"}],"version-history":[{"count":4,"href":"https:\/\/salesforcechronicles.com\/index.php?rest_route=\/wp\/v2\/posts\/1802\/revisions"}],"predecessor-version":[{"id":1836,"href":"https:\/\/salesforcechronicles.com\/index.php?rest_route=\/wp\/v2\/posts\/1802\/revisions\/1836"}],"wp:attachment":[{"href":"https:\/\/salesforcechronicles.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1802"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/salesforcechronicles.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1802"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/salesforcechronicles.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1802"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}