Business 360 FEP Connector > Mappings with the Business 360 FEP connection > Target transformation in mappings
  

Target transformation in mappings

In a mapping, you can configure a Target transformation to represent MDM SaaS assets. If you want to write data to part of an asset data in Business 360, use a Business 360 FEP connection.
The following table describes the properties of a Target transformation that uses the Business 360 FEP connection:
Property
Description
Name
Enter the target name.
Description
Enter a description for the target.
Incoming Fields
Lists all the incoming fields from the Source transformation. You can set field rules and rename the fields.
Connection
Choose a Business 360 FEP connection to write data to specific set of fields within the MDM SaaS assets.
Target Type
Type of the target object. Select Single Object.
Object
Select the asset and its object to which you want to write data. For example, you can choose to write data to root fields or fields of a field group in a business entity.
Operation
Choose the type of operation that you want to perform.
You can select one of the following operations:
  • - Insert. Adds new records and overwrites all the field values of existing records.
  • - Update. Updates field values in record sections.
    • To update any root field value or field values in field group entries, ensure that you select the update operation for the target transformation of the root field and the field group entry.
    If you want to add a new field group, you can specify the update operation for the target transformation of the field group.
  • - Upsert (Update or Insert). Adds new records and overwrites all the field values of existing records.
    • When you specify the upsert operation, ensure that you map all the fields. If you map only the fields that you want to update, the upsert operation updates the specified field values and sets the other field values to null.
  • - Delete. Performs the following operations:
    • - Deletes field group entries in record section.
      • If you want to delete a specific root field value, ensure that you don't pass the value of that particular field.
      You can't use the delete operation to delete the hierarchy and relationship records.
    • - Deletes source records.
In the Advanced section, you can select Restore Deleted Records to restore the deleted source records. To use this option, you must first select the Update operation.
Target Fields
Lists all the target fields based on the selected object. You can add fields, delete fields, and edit metadata of the fields.
Field Mapping
View all the input fields and target fields. Drag the fields to map them. Optionally, you can use the Smart Map and Automap options. For more information about these options, see the Informatica Cloud Data Integration help.
When you create a mapping to ingress data to a dynamic field definitions attribute, map the following target fields:
  • - DynamicFieldTemplate. Internal ID of a field in the dynamic pool.
  • - Mandatory. Indicates whether the field is required. To set the field as a required field, set the value to 1. Otherwise, set it to 0.
  • - InheritanceMode. Indicates whether the related records inherit dynamic field definitions from parent records. Default is PASS. Set the value to one of the following modes:
    • - NONE. The related records won't inherit dynamic field definitions.
    • - START. The related records inherit dynamic field definitions. Any changes to the dynamic field definitions are inherited by the related records.
    • - PASS. The current and related records inherit dynamic field definitions from parent records.
    • - STOP. The current record has inherited the dynamic field definitions previously from parent records. Any changes to the dynamic field definitions aren't inherited by the related records.
    • - DISABLED. The related records won't inherit dynamic field definitions. The dynamic field definition for the current record is not available.
  • - ParentId. Source primary key of the record to which you add the dynamic field definition.
  • - SourcePKey. Unique identifier of the dynamic field definition that you add to the record.
After you ingress data to a dynamic fields definition attribute, ensure that you run the process hierarchies job to index records and to process the inheritance of dynamic field definitions within a searchable hierarchy.
For more information about dynamic field definitions and process hierarchies jobs, see the Business 360 Console help.
When you create a mapping to ingress data to dynamic field values attributes, map the following target fields:
  • - ParentId. Source primary key of the record that you add the dynamic field values to.
  • - Identifier. Path to the dynamic field. The identifier is separated by a period (.) for fields within the nested field group. To locate an identifier within the dynamic pool, you can use the internal ID of the field.
  • - Value. Value of the dynamic field.
  • - SourcePKey. Unique identifier of field groups and nested field groups.
  • - ParentSourcePKey. Unique identifier of the nested field group. For root fields and parent field groups, the value is empty.
  • - sourceLastUpdateDate. Indicates the source last updated date of a dynamic field group. When you map the sourceLastUpdateDate for dynamic fields or dynamic nested field groups, the values are ignored without any notification.
The following table lists examples of target fields used to ingress dynamic field values:
Identifier
Value
SourcePKey
ParentSourcePKey
ParentId
sourceLastUpdateDate
cooking_instructions
Boil Water, add salt, cook for 6 minutes
BorgesPenne
pasta_shape
Penne
BorgesPenne
color
High Risk Red
Retaliate2
size
10.5
Retaliate2
camera
mainCamera
myPhone20
2024-01-01T03:00:00.000Z
camera.resolution
mainCameraSuperResolution
mainCamera
myPhone20
camera.resolution.resolution_value
48.0
mainCameraSuperResolution
myPhone20
camera.resolution.resolution_unit
MP
mainCameraSuperResolution
myPhone20