[Remote key]. A single-valued text field that contains a key value for the corresponding remote system. This is a qualifier field.
In effect, each remote systems Table Record becomes a record of the key mapping qualified lookup table, and each actual key mapping becomes a link of the key mapping qualified lookup field.
In the primary data, other systems also transmit data. Other systems are called remote systems. When a primary data is associated with a primary data, key mapping is generally used, the field is called the remote key. The remote key is invisible in Data Manager and can be viewed using the console tool. Here we mainly discuss the issues that need to be paid attention to when adding data.
For example, there are two primary data, A and B, and there is a relationship between A and B in A. This relationship is updated by remote system. Because primary data of B is used by, generally, these two primary data are placed under the same repository. Therefore, when creating the primary data, the key mapping option is selected. The remote system enters MDM in the form of port XML, when the external system passes in the relationship between A and B, the system will find the remote key of B's primary data for the relationship in A. If B has just entered the data in, if the remote key is not found, Mdm automatically generates a remote
Key data, which is certainly not our normal data. Therefore, when we create data in B, we must add the remote key to each piece of data.