Mapping Data Streams | Data Cloud Decoded

Поділитися
Вставка
  • Опубліковано 22 жов 2024

КОМЕНТАРІ • 9

  • @srigorla
    @srigorla Рік тому

    Do we need to map Contact to Individual Data Model entity in here, so that it can come handy for identity resolution later?

  • @AnnaSzabo
    @AnnaSzabo Рік тому +1

    Going through trails AND watching this playlist REALLY helped me out a lot! Thank you

  • @JohnDeMars
    @JohnDeMars 4 місяці тому

    I like the view on the home page. How can i get the same?

  • @SalesforceUSA
    @SalesforceUSA Рік тому

    Very good video

  • @quintessence4736
    @quintessence4736 5 місяців тому

    Wouldn't the Contact DLO Contact ID be mapped to a Contact ID foreign key field on the Contact Type Email/Phone/Address DMOs, rather than the PK ID fields of those objects? Those Contact Type IDs are unique and don't exist in the Contact Records do they?

  • @memetemplates001
    @memetemplates001 8 місяців тому

    I couldn't understand why we need to make Data Lake Object to Data Model Object? We are already having data in Data Lake Object.

    • @daniellelarregui4334
      @daniellelarregui4334 7 місяців тому +1

      The data lake object is just the initial container to hold your data that is coming in from Data Streams. Data Model Objects are Data Cloud's canonical data model.There is some functionality in Data Cloud like identity resolution jobs that only use data stored in DMOs.

    • @dodifriedenberg8077
      @dodifriedenberg8077 2 місяці тому +2

      This is one the benefits of Data Cloud. Fields for the same thing coming in from different sources could have wildly different names. By mapping them to the DMOs, you're teaching Data Cloud to treat these different incoming fields as the same field/kind of data.

  • @VamseeVVR18
    @VamseeVVR18 Рік тому

    Hi Salesforce devolopers can you provide for me Salesforce Administrator videos