Loading
Salesforce Enforces New Security Requirements in Summer 2026Read More
Sales Basics
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Create DLOs for Your Standard Objects

          Create DLOs for Your Standard Objects

          If you can't deploy the Forecasting data kit, you can manually configure data streams and DMO mappings for the standard objects.

          Required Editions

          Available in: Lightning Experience
          Available in: Enterprise, Unlimited with Sales, and in Agentforce 1 Sales Edition

          In Data 360, create data streams to begin the flow of data from the standard objects to Data 360. You also create a data lake object (DLO) while you create a data stream.

          Create data streams and DLOs for these objects.

          Standard DLOs
          Objects Data Stream and DLO Names
          Account Account
          User User
          UserRole UserRole
          Period Period
          FrcstCustmzAdjustment FrcstCustmzAdjustment
          FrcstCustmzOwnerAdjustment FrcstCustmzOwnerAdjustment

          See Create a Salesforce CRM Data Stream.

          Important
          Important

          In case of the FrcstCustmzOwnerAdjustment object, the Forecasting Customized Owner Adjustment ID field has more than 40 characters. Rename it to Forecasting Custmz Owner Adjustment ID to bring the character count down. Otherwise, you encounter an error.

          Map DLOs with DMOs

          After you create DLOs for your objects, create data model objects (DMOs) for each DLO and map them respectively. Use the same names of the DLOs to name the DMOs. See Map Data Model Objects.

          Map your User and UserRole standard DLOs to the corresponding DMOs that are prefixed with ssot to avoid an error message stating that the DMO already exists. Make sure that the fields in the DLOs are mapped to the appropriate fields in the corresponding DMOs as mentioned in these tables.

          User
          DLO field labels (api names) map to the dmo field labels (API Names)
          Full Name (Name__c) Full Name (FullName__c)
          User ID (Id__c) User Id (Id__c)
          Role ID (UserRoleId__c) User Role (RoleId__c)
          Photo (SmallPhotoUrl__c) Small Photo Url (SmallPhotoUrl__c)
          UserRole
          DLO field labels (api names) map to the dmo field labels (API Names)
          Name (Name__c) Role Name (Name__c)
          Role ID (Id__c) Role Id (Id__c)
          Parent Role ID (ParentRoleId__c) Parent Role (ParentRoleId__c)
          User ID (ForecastUserId__c) Forecast User (ForecastUserId__c)
           
          Loading
          Salesforce Help | Article