Data maps

Data maps are a means of identifying related records among separate tables in ITSMA Service Management. Service Management applies data map queries to each record returned in a purge or archive selection query. For example, if during the purge and archive process you select 10 probsummary records, then Service Management uses the probsummary data map to search for related records on each of the 10 records.

When you enable a data map, Service Management returns a list of additional related records for each purge or archive record queried. Service Management purges or archives these related records along with the original records you selected during the purge and archive process. For example, using a data map on 10 probsummary records may result in 30 actual records being purged or archived.

Note: Using data maps can greatly increase the number of records that you purge or archive. Since there is no limit on the number of data maps that you can define, there can potentially be a large number of mappings for any given table.

Tip: To prevent the accidental loss of substantial numbers of records, use the purge and archive function to save copies of your records to an external table before deleting them. This enables you to restore any records that you may have deleted accidentally.

By default, Service Management has 155 pre-defined data mappings that you can use to purge or archive records and forms. These mappings contain the most commonly purged or exported records and tables. If you add custom tables and fields to your Service Management system, you may want to create custom data mappings to purge or archive any related records based on these custom tables.

To create data mappings to related records, you must know the primary key fields and join fields used by your Service Management tables. You must also know how to write Service Management queries using escaped characters, special operators, and RAD variables.