A column map provides specifications needed to match or exclude columns from processing in a data management service. Convert, insert, and load services must reference a table map, which may reference one or more column maps. You can use a column map to define data transformations with privacy policies or column map procedures.
When you create a new column map, you must choose a file as the source for the columns you want to map. Similarly, you must specify a data store alias for the target data.
Column maps stored in the Optim™ directory are available for reuse or sharing with other users. A local column map is stored as part of a data management service and is otherwise not available for other services. If the associated table map is local to a service, both the table map and column map are available only to the specific service.
The fully qualified name of a column map has two parts: identifier.name.
When you create column maps, it is helpful to use a logical set of naming conventions to identify and organize definitions for easy access.