Create DMOs for Consumption-Based Data

The consumption-based data includes details of real usage and estimates of future usage of each product or service that you want to forecast.

Required Editions

Available in: Lightning Experience

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

You need two DMOs, one for tracking the consumption lifecycle of a product or service line item used by customers and another for tracking customer usage data and other consumption details. For example, to forecast consumption for your computing storage business, create DMOs with the details and fields provided in these tables. See Create a Custom Data Model Object.

Product or Service DMO
Details	Values
Object Label	StorageService
Object API Name	StorageService
Object Category	Other

Field Label	Data Types
OrganizationId	Text
Id	Text (Primary Key)
Name	Text
Account Lookup	Text
Owner	Text
ContractValue	Number or Currency The data type of this field is the same as that of the field on which you want to apply custom adjustments.

Consumption Data DMO
Details	Values
Object Label	StorageUsage
Object API Name	StorageUsage
Object Category	Other

Field Label	Data Types
OrganizationId	Text
Id	Text (Primary Key)
Storage Service Lookup	Text
Date	DateTime
MeterAmount	Number
Expected	Number
Predicted	Number

Note

In your consumption data DMO, make sure that you at least have one field of the DateTime data type and one field of the Number or Currency data type.

Create and Map DLOs with Consumption-Based DMOs

Create DLOs to begin the flow of the consumption-based data from your data sources. You can create a custom object, use a preexisting object within Salesforce CRM, leverage Amazon S3, or choose other options to establish these DLOs.

You need two DLOs, one for the product or service DMO and another for the consumption details DMO. For the computing storage business example mentioned above, use the information provided in these tables to map DLOs with the respective DMOs. We recommend that you name the fields in DLOs the same as the field names in DMOs for easy mapping. See Map Data Model Objects.

StorageService
DMO Fields	Map to the Field That Contains...
Id (Primary Key)	Unique IDs.
Name (Name__c)	Names of services.
Account	Account IDs of services. The account IDs must match the IDs in the Account object.
Owner	Owners (user IDs) of services. The user IDs must match the IDs in the User object.
OrganizationId	Use the 18-character organization ID. To find it, open Developer Console and run this query in Query Editor: `SELECT Id, Name FROM Organization`

StorageUsage
DMO Fields	Map to the Field That Contains...
Id (Primary Key)	Unique Ids.
Usecase	Service IDs. The service IDs must match the IDs in the service DMO.
MeterDate	The date and time of the consumption.
MeterAmount	The amount of the consumption for each use case.
Expected	Data of expected consumption for each use case.
Predicted	Data of predicted consumption for each use case.
OrganizationId	Use the 18-character organization ID. To find it, open Developer Console and run this query in Query Editor: `SELECT Id, Name FROM Organization`

Note

The unique ID of any data imported from an external source must be exactly 15 characters.