Migrate Data Prep for custom fields to the new streaming media fields
This document describes the process of migrating the Data Prep service that exists on top of the Adobe Data Collection flows that are enabled for Adobe Streaming Media Collection data. The migration converts a Data Prep mapping from the Adobe Streaming Media Collection data type called “Media” to use the new corresponding data type called “Media Reporting Details.”
Migrate Data Prep for custom fields
To migrate the Data Prep mappings from the old data type called “Media” to the new data type called “Media Reporting Details,” you must edit the Data Prep mappings:
mediaReporting fields before completing the steps in this section.-
In Adobe Experience Platform, under the Sources section, go to the Dataflows tab.
-
Locate the dataflow responsible for importing streaming media data from Adobe Analytics to Adobe Experience Platform via Adobe Data Collection.
-
Select Update dataflow to modify the Data Prep setup by replacing every custom source mapping that contains a deprecated field with the new corresponding field from the new XDM object.
-
Locate the mappings containing source fields from the deprecated “Media” object.
-
Replace those sources by using fields from the new “Media Reporting Details” object.
-
Validate that the mappings are still working as expected.
See the Content ID parameter on the Audio and video parameters page to map between the old fields and the new fields. The old field path is found under the “XDM Field Path” property while the new field path is found under the “Reporting XDM Field Path” property.
Example
To make it easier to follow the migration guidelines, consider the following example dataflow that contains a single mapping. In this case, you need to apply the migration guidelines only once.
-
In Adobe Experience Platform, under the Sources section, go to the Dataflows tab.
-
Locate the dataflow responsible for importing streaming media data from Adobe Analytics to Adobe Experience Platform via Adobe Data Collection.
-
Select Update dataflow to enter the editing UI as shown in the below image.
-
In the Mapping tab, select Custom.
-
Identify the custom mappings that rely on
media.mediaTimedfields as sources.
In this example, because you created a custom field group on the schema in your development organization, the target field is under
_dcbl. The custom field group path differs based on the organization name. -
For each mapping that uses the
media.mediaTimedobject, find its correspondent in themediaReportingobject using this documentation.As an example, for Network, the correspondent for
media.mediaTimed.primaryAssetViewDetails.broadcastNetwork ismediaReporting.sessionDetails.network.
-
In the Source field field, replace the
media.mediaTimedpath with themediaReportingpath. The target field remains unchanged.
-
Select Next to save your changes.
The status shows as Processing. After the changes are applied, the status shows as Enabled.
Example with different data types
In the above example, all of the data types involved were String, so the mapping replacement was direct.
If the source field data type is different than the target field data type, you need to follow the guidelines in the Data Prep troubleshooting guide, Handling data formats with Data Prep, and Data Prep mapping functions.
For example, if the source type is a string and the target type is a boolean, Data Prep can automatically parse the value and convert the source value to a boolean.
If the source type is a number and the target type is a boolean, you need to use data manipulation functions:
Mapping with media.mediaTimed to a custom field.
Mapping with mediaReporting to the same custom field:
