Copy a Source Field to a Destination Field

You can use a data modify action to copy a field from a source MDC or virtual field to a field in a destination MDC or virtual field.

Before you begin

If you are creating a data modify action to:
  • Set call out request fields, you must have already created the LDAP call out action that will be referenced in the data modify action.
  • Set or copy workspace fields, you must have already created the custom workspace that will be referenced in the data modify action.
  • Copy metadata from a normalizer, you must have already defined the metadata in the normalizer.
  • Copy metadata from a rate table or a policy table, you must have already defined the metadata in the table.

About this task

Perform this task to configure a data modify action for copying a source field to a destination field. You can copy fields from the following sources:
  • Message — To copy fields from a message MDC or virtual field.
  • Object — To copy fields from a subscription, group, device, or user object.
  • Call Out Response — To copy fields from the MtxLdapResponseDataExtension MDC, one of its descendants, or a virtual field.
  • Workspace — To copy fields from a custom workspace MDC.
  • Metadata — To copy fields from metadata in a normalizer, rate table, or policy table.
You can copy fields to the following destinations:
  • Message — To set fields in a message MDC or virtual field.
  • Call Out Request — To set fields in the MtxLdapRequestDataExtension MDC, one of its descendants, or a virtual field. Use this destination to set fields in the custom MDC specified in the LDAP call out request selected in this data modify action. The request call out action and the data modify action must both be assigned to the same PreRating profile.
  • Workspace — To set fields in a custom workspace MDC.
  • Object — To set fields in a subscription, group, device, user, or an offer object.

Procedure

  1. Create a new data modify action or edit an existing one. To edit an existing data modify action, in Data Modify Actions, click the name of the action you want to edit or click Edit the selected object.
    For information about creating a data modify action, see the discussion about creating a data modify action.
  2. In Start Date/Time, use the date picker to select the date on which the object becomes active in the Pricing database and is first available for use, or enter the date in the format YYYY-MM-DD. Optionally, enter a time for when the object becomes active. The default start date/time is 2000–01–01 00:00:00. If applicable, the range in which the start date/time must fall is listed. For example:
    • Select a date on or before 2021–12–01.
    • Select a date on or after 2020–01–27.
    • Select a date between 2000–01–02 and 2021–10–04.
    Note: If you are creating a new revision of this object, the start date/time must be after the start date/time of the preceding revision and before the start date/time of the next revision. If you are making a copy of this object, the start date/time is not copied. The new object is the first revision, so it has the default start date/time of 2000–01–01 00:00:00.
    By default, data modify actions are active immediately. If you are creating a new revision of a data modify action, you must not change the source type.
  3. In Source, select one of the following.
    • Message or Object — To copy fields from a message MDC, a subscription, group, device, or user object, or a virtual field.
    • LDAP Call Out Response — To copy a field from an LDAP call out response.
    • Workspace — To copy a field from a custom workspace.
    • Metadata — To copy a metadata field from a normalizer, a rate table, or a policy table.
  4. If you selected Message or Object:
    1. In Source Container, select the MDC or virtual field that has the field you want to copy.
    2. In Source Field, select the field that you want to copy.
    3. (Optional) If the source container is an MtxGroupObject MDC or a descendant of MtxGroupObject, in Tier Name, enter the group tier to use.
      If set, MATRIXX retrieves the DMA source object based on the specified tier. If the group does not have a tier, MATRIXX considers the source field to be empty and processes it according to the action selected in Source Action.
      If the tier is not set, MATRIXX retrieves the source object associated with the group initiator.
      Note: If the initiator is a subscriber or device and the tier is not specified, MATRIXX considers the source field to be empty and processes it according to the action selected in Source Action.
  5. If you selected LDAP Call Out Response:
    1. To copy from:
      • A calling party response field, select Calling.
      • A called party response field, select Called.
    2. In Source Container, select the MDC or virtual field that has the field you want to copy.
    3. In Source Field, select the field that you want to copy.
  6. If you selected Workspace:
    1. In Type, select the workspace type.
    2. In Source Container, select the MDC that has the field you want to copy.
    3. In Source Field, select the field that you want to copy.
  7. If you selected Metadata:
    1. In Type, select:
      • Matrix — To copy a metadata field from a rate table or a policy table.
      • Normalizer — To copy a metadata field from a normalizer.
    2. If you selected Matrix, in Pricing Object, select the metadata source, and in Table, select the policy or rate table that has the metadata you want to copy.
    3. If you selected Normalizer, in Normalizer, select the normalizer to use as the source for the metadata.
    4. In Metadata Name, select the name of the metadata you want to copy. If the metadata type is Normalizer, you can use normalizer results fields for the source. Select --Name-- for the name field or --Description-- for the description field.
      Note: My MATRIXX raises a warning if the data modify action refers to a normalizer name or description field for a normalizer that also uses chaining on those fields.
  8. In Source Action, select the action to take if the source field is empty from the following options:
    • Do Nothing if Source Empty.
    • Fail if Source Empty — If the source field is empty, log an error.
    • Take Default if Source Empty — If the source field is empty, use the default value to set the destination field. If the default value is not set, log an error.
  9. If you set Source Action to Take Default if Source Empty, in Default if Empty, enter the value to use if the source field is empty.
  10. To copy the source field to a field in a message:
    1. In Destination, select Message.
    2. In Destination Container, select the message MDC or virtual field that has the field you want to modify.
    3. In Destination Field, select the field that you want to modify.
  11. To copy the source field to a field in an LDAP call out request:
    1. In Destination, select LDAP Call Out Request.
    2. In Call Out Name, select the name of the LDAP call out action that you want to use.
      If selecting an MDC as your destination container, the selected call out action determines which type of MDC is used (based on the MtxSubscriber InfoQueryObject.ExtensionName field value) as the destination container for this data modify action.
    3. In Destination Container, select the MDC or virtual field that has the field you want to modify. Valid containers are the MtxLdapRequestDataExtension MDC or its descendants.
    4. In Destination Field, select the field that you want to modify.
  12. To copy the source field to a field in a workspace:
    1. In Destination, select Workspace.
    2. In Type, select the workspace type.
    3. In Destination Container, select the workspace MDC for the selected workspace type.
    4. In Destination Field, select the field that you want to modify.
  13. To copy the source field to a field in an object:
    1. In Destination, select Object.
    2. In Destination Container, select the object that has the field you want to modify.
    3. In Destination Field, select the field that you want to modify.
  14. In Destination Action, select one of:
    • Create if Absent — If the source field is present, copies the source field to the destination field only if the destination field is not set already. If the destination field already has a value, it is not updated.
      If the source field is empty and Source Action is set to:
      • Do Nothing if Source Empty — Does nothing.
      • Take Default if Source Empty — Uses the default value to set the destination field only if the destination field is not set already. If the default value is not set, logs an error.
      • Fail if Source Empty — Logs an error.
    • Create or Update — If the source field is present, uses the source field to set the destination field or update the destination field value.
      If the source field is empty and Source Action is set to:
      • Do Nothing if Source Empty — Does nothing.
      • Take Default if Source Empty — Uses the default value to set the destination field. If the default value is not set, logs an error.
      • Fail if Source Empty — Logs an error.
  15. Click Save.