DspMigrate: Using Metric Groups

DSP's dspMigrate is the premier migration/conversion tool essential to any ETL solution. One of the many features dspMigrate has to offer is its control over every aspect in the migration process. From setting up secondary data sources, to enabling a host of field options, to determining what data to output upon load, the application is dsp's one-stop shop for multiple scenarios in an enterprise's data integration project.

In particular, there may be a need to determine which fields should get priority treatment over others upon entering the mapping process. DspMigrate offers such a solution in the form of Metric Groups. For example, some fields may need to take priority while mapping due to a field's high visibility or interest in a project. Applying a Metric Group to a field or fields would accomplish this.

Metric Group Setup

Similar to Field Groups, a Metric Group is set up in Design under Configuration.

1. Click Add to add a new Metric Group.
2. Choosing a priority is key. There already exists a Default Group, which is applied to all fields unless otherwise assigned. Therefore, to control the listing of a field in Map, a user would have to create a new Metric Group with a smaller number priority (<10) so that it will be listed prior to the fields with the default Metric Group (priority 10) or other Metric Groups with higher priorities.
3. Conversely, if the need is to have a lower priority field to map, then a user would add a Metric Group with a higher priority (>10) so it would appear further down in a target's list of fields when viewed in Map.
4. When activating all relevant fields within a target, users would edit the field record and choose which Metric Group is required.
5. When Sync to Map is performed, fields will list according to their Metric Group(s).

NOTE: A Metric Group does not drive priority assigned in Transform's Target Source Rule level. Such priority is determined by the Field Order ID number found in the list of available fields in Target Design. To increase or decrease the priorities assigned to a general source rule (non-key rule), a user would edit the record for a field in Design so it would reflect upon building the rule with AutoGen and list in Transform list of source rules.

BackOffice Associates offers professional, instructor-led training in an interactive hands-on style. To view the latest schedule of classes currently offered, visit http://www.boaweb.com/company/product-training/