cli:mapping
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
cli:mapping [2019/11/04 22:29] – [Location] Scott Cunliffe | cli:mapping [2025/01/21 22:07] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Customer Mapping ====== | ====== Customer Mapping ====== | ||
- | The Customer Mapping file contains a mapping of your TapeTrack Customer-ID to your Iron Mountain Account Code and vise versa. | + | The Customer Mapping file contains a mapping of your TapeTrack |
The mapping from TapeTrack to Iron Mountain is used when sending data to Iron Mountain and the reverse mapping, from Iron Mountain to TapeTrack, is used for the reconciliation process. | The mapping from TapeTrack to Iron Mountain is used when sending data to Iron Mountain and the reverse mapping, from Iron Mountain to TapeTrack, is used for the reconciliation process. | ||
Line 11: | Line 11: | ||
===== Example ===== | ===== Example ===== | ||
- | CustomerMapping.txt, | + | CustomerMapping.txt, |
The table values are searched sequentially, | The table values are searched sequentially, | ||
- | It is important that entries are present to both match the Customer-ID to the Iron Mountain Account Code as well as the Iron Mountain Account Code to the Customer-ID (e.g. '' | + | It is important that entries are present to both match the [[object: |
- | <sxh> | + | <code> |
# | # | ||
# This file contains a mapping of your TapeTrack Customer-ID to your Iron Mountain Account Code and vise versa. | # This file contains a mapping of your TapeTrack Customer-ID to your Iron Mountain Account Code and vise versa. | ||
Line 29: | Line 29: | ||
ACME=99999 | ACME=99999 | ||
99999=ACME | 99999=ACME | ||
- | </sxh> | + | </code> |
cli/mapping.1572906542.txt.gz · Last modified: 2025/01/21 22:07 (external edit)