You are here:
Create Data Streams and Data Lake Objects
Create data streams and data lake objects (DLO) to connect and associate your data with the information that is stored in Data 360. This process creates a unified view of your service history for better analysis and insights into your service operations.
To ensure a smooth setup, confirm the following:
- Default Namespace: Ensure your Data Lake Objects (DLOs) and Data Model Objects (DMOs) are in the default namespace to simplify mapping.
- Data Scope: Configure your process to include all new and closed repairs. You can filter out work orders related to routine preventive maintenance.
- Multiple Data Sources: If bringing in data from more than one org, remember to set up fully qualified keys to keep your records distinct. Learn more about keys.
Set Up Data Streams
Data streams are the pipelines that bring your source data into Data 360.
- Create data streams for your Asset, Work Order, Work Type, and other related objects.
- Once created, update your input data sources to use these new streams.
If a stream uses data from a single org, you can keep the name simpler by omitting the org prefix. Learn more about CRM data streams.
Create the Asset Service Action Data Lake Object (DLO)
Create the core objects using the pre-configured data kit. Learn more about batch transforms.
- In Data Cloud, on the Data Transforms tab, click New.
- Select Create from a Data Kit, and click Next.
- Select the Create Asset Service Action BDT.
- Click Create. This action builds the Batch Data Transform (BDT) and its associated Data Lake Object (DLO) for you.
- Run the batch data transform. For more information, see Run Batch Data Transforms.
Configure the Asset Service Action DLO
After you create the objects, review and configure the DLO.
- From App Launcher, select Data Cloud and click Data Lake Objects.
- Find the DLO that you just created.
- Confirm or set the following names:
- Data Lake Object Name: Asset Service Action
- Data Lake Object API Name: AssetServiceAction
- Review the standard fields and add any custom fields your analysis requires.
Map Your Data Fields
This crucial step tells Data 360 how to connect fields from your source DLOs to your target DMO. Go to the Data Streams tab, search for and click the data stream you want to map, and click Start Data Mapping.
- If the field names in your source data match the API names in the target DMO, Data 360 can map them automatically.
- In the Batch Data Transform, map the required source fields. Use the Rename Column function for any source fields that do not match the target DMO field names.
These field mappings are required:
| Source Data (from DLOs) | Target DMO Field |
|---|---|
| Work Order or Case Data | |
| Work Order/Case ID | Id |
| Repair Status | Status |
| Repair Start Date | StartDate |
| Repair End Date | EndDate |
| Record Creation Date | CreatedDate |
| Repair Type ID (WorkTypeId) | AssetServiceTypeIdentifier |
| Repair Type Name (WorkType.Name) | AssetServiceActionType |
| Asset Data | |
| Asset ID | AssetId |
| Product-related fields | SKU, Family, Product2Id |
| Asset Install Date | InstallDate |
| Asset usage and unit of measure fields | Usage, UnitOfMeasure |
Run and Verify Your Work
With the mapping complete, process the data and check the results.
- Click the Data Transforms tab. If the Data Transforms tab isn’t visible, click the More tab and select Data Transforms.
- On the Recently Viewed screen, click the triangle to the right of the batch data transform name you want to run, and select Run Now.
- Verify that the Asset Service Action DLO is correctly mapped to the Asset Service Action DMO within the transform. If you added custom fields, ensure they are also created in the DMO and included in the mapping.
Inspect the results using the Data Explorer. Check that the Asset Service Action DMO is populated with data and that key fields are accurate. For more information, see Map Data Model Objects.
