An Object must have a field that identifies it uniquely if you wish to import the Object in Synexsys repeatedly with the SXSimport module. This field will allow Synexsys to find the target Object and merge the existing information with the data from the source Object. If, for instance, you have chosen to manage users in Synexsys, you can define their employee number and their unique Identifier (Merging Key). This way, you could import the list of users from Synexsys daily and update this information without creating duplicates, since the employee number is a constant value.
When it is a PC type Object, the Synexsys audit mechanism is in charge of this identification. During the first audit, an identification file name SID.TXT is placed in the machine. Then, during later audits, Synexsys will recognise the machine using the Identifier and will merge new collected data with the existing information.
Therefore, there are two good reason why you should define a Merging Key for a PC type Object:
![]() |
The first is that if the SID.TXT identification file disappears (crash or disk cloning), Synexsys will no longer be able to use this key to merge the collected information. To solve this problem, Synexsys has several mechanisms that allow it to rebuild a SID.TXT file on the new disk and merge the audit with the original PC data that is contained in the Synexsys database. (more information on PC merge mechanisms) |
|
|
![]() |
The second reason may also be interesting (and necessary) if you plan to later complete the technical information collected by the Synexsys agent with data from another source using Synexsys Import. |