erwin Data Transformation 9.2.6 - User Guide

Delete in CM Repository

Delete in CM Repository

When selecting this operation, the only mandatory mapping is the NAME of the object type that the user wants to manage: as a result of this operation, data coming from the source adapter will be physically deleted in the specified model accord to the defined mapping rules, for the ones that are not diagrammed (while diagrammed ones will be listed in the operation log file).

Synch in CM Repository

Synch in CM Repository

When selecting this operation, it is mandatory that user choose a keyset that’s unique in the source dataset to avoid undesired results. In particular:

•Objects coming from the source dataset will be inserted/updated in the specified model accord to the defined mapping rules

•Objects already in the specified model object type, that are not listed in the source dataset, will be:

oWhen “logical” option is set, logically deleted, and renamed with the prefix “_TO_BE_DELETED_”

oWhen “physical” option is set, physically deleted, if not diagrammed, or renamed with the prefix “_TO_BE_DELETED_” if diagrammed

oWhen “physical forced” option is set, physically deleted, even if diagrammed

If the synchronization operation must be done against a subset of objects, and not the whole set of instances (for example, when contributing external source are more than one for a given object type, each one managing a set of instances, like a CMDB providing data for “Applications in Production environment”), this can be managed using the sync filters interface.

Double clicking on the “filter” icon on object type column name

Opens a popup window allowing the creation of sync filters and showing previously defined filters:

User can add, delete (uncheck the filters to be deleted) and apply desired filters.

When the sync operation is defined to be executed according to filters, the involved object type name will be marked with a specific filter icon in the map table, the name will be plain otherwise:

For filtered sync option, the load step will follow the usual behavior, while the deletion of redundant object instances will be done within the filtered subset on objects compliant with the filters.

POST to EA Agile

POST to EA Agile

In the “Workspace Name” the name of target workspace will be shown.

User may proceed with the mapping operation in the mapping table, having the requested parameters described in the following list:

Column Name: shows the columns coming from the data source and from the transformation steps; a sequence number that the system assigns to each data source can be seen as prefix to the column name, so the user can easily recognize the source of the data, in the case of multiple data sources.

Column type and format: choose the type and format of the column of the source (String, numeric, boolean, date). This is important if user wants DT to perform a re-format operation on the target column data type.

Date in UTC format

Date / Datetime

The following ISO-8601 formats are supported:

•YYYY-MM-DD (e.g. 2019-01.28)

•YYYY-MM-DDThh:mm (e.g. 2019-01-28T01:02)

•YYYY-MM-DDThh:mm:ss (e.g. 2019-01-28T01:02:03)

•YYYY-MM-DDThh:mm:ssTZD (e.g. 2019-01-28T01:02:03+04:05)

When positing to EA Agile, if a time and offset are not provided, these will default to 00:00Z (i.e. 00:00+00)

Date Ranges

For the supported UTC date formats outlined above, DT supports the following separators:

•$UTCDATE/$UTCDATE

•$UTCDATE,$UTCDATE

•$UTCDATE;$UTCDATE

•start:$UTCDATE end:$UTCDATE

•start: $UTCDATE end: $UTCDATE

Date in EUR format

Date / Datetime

The following formats are supported:

•dd/MM/yyyy (e.g. 28/01/2019)

•dd/MM/yyyy HH24:mm (e.g. 28/01/2019 13:01)

•dd/MM/yyyy HH24:mm:ss (e.g. 28/01/2019 13:01:02)

•dd/MM/yyyy HH:mm AM/PM (e.g. 28/01/2019 01:01 PM)

•dd/MM/yyyy HH:mm:ss AM/PM (e.g. 28/01/2019 01:01:02 PM)

•dd/MM/yyyy HH:mmAM/PM (e.g. 28/01/2019 01:01PM)

•dd/MM/yyyy HH:mm:ssAM/PM (e.g. 28/01/2019 01:01:02PM)

Date Ranges

For the supported EUR date formats outlined above, DT supports the following date range formats:

•start:$EURDATE end:$EURDATE

•start: $EURDATE end: $EURDATE

•$EURDATE;$EURDATE

•$EURDATE,$EURDATE

Date in USA format

Date / Datetime

The following formats are supported:

•MM/dd/yyyy (e.g. 01/28/2019)

•MM/dd/yyyy HH24:mm (e.g. 01/28/2019 13:01)

•MM/dd/yyyy HH24:mm:ss mm (e.g. 01/28/2019 13:01:02)

Date Ranges

Dates ranges may be formatted as:

•start:$USADATE end:$USADATE

•start: $USADATE end: $USADATE

•$USADATE;$USADATE

•$USADATE,$USADATE

This input date format has to be set in workflow mapping step:

Object type: choose the model object type to load the data; it’s possible to select different object types in the same operation

Mapping (prop./assoc.): once you have selected the object type you can map the property or the association between the ones defined in EA Agile for that object type.

 About associations mappings, multiple values can be associated putting the different values in a single cell, newline separator.  Other separators can be replaced with “Data Formatting: Replace Text”:

If an association is of “composition” type, like “Entity is part of Data Model”, the action “set as parent” must be selected from drop down list in order to properly identify objects parent in the platform.

Type: shows the type of the mapped column of the target (String, numeric, boolean, date). To help the user in mapping, in case of list or key values allowed values are shown in the “type” cell tooltip:

No New: when importing data from an external source, it’s possible that the master list of objects involved in the operation is the one contained in the workspace. In such a case, the user would want existing objects to be updated (only for the properties used in mapping), but no objects from being created. If so, the user may choose to check the “No New” option, on the keyset of the master object type, and this will prevent new objects from being created, while existing will be updated within bounds of mapped properties.

The same applies when the object list which has not to be extended is the one related to an object type associated with the master, involved in the operation. In such a case, user may choose to check “No New” option, on the record related to the association, and this will prevent new associated objects from being created.

Delete in EA Agile

Delete in EA Agile

When selecting this operation, user should map only the “Name” of the object type that he wants to manage: as a result of this operation, data coming from the source adapter will be deleted in the specified workspace according to the defined mapping rules.