Sync audits
A GIS mapping can be configured to create sync audits for all records, to create sync audits only for records with errors, or not to create any sync audits.
Use Lookup Sync Audit to review sync audits. You can also use the Sync Batch InfoViewer to review the audits for a specific batch. You can then open a sync audit in the Sync Audit InfoViewer, which displays more detailed information such as the mapped fields, the actions taken, and any error messages. You can also use the lookup or the InfoViewer to process sync audits.
Each sync audit has a condition and a status, which together summarize the results of the audit. This table shows the different sync audit conditions:
Condition | Description |
---|---|
Data Mismatch | One or more fields have different values in the two datasets. |
Duplicate | A record was found with the same business key as another record
in the dataset. The sync audit status for a duplicate record is Analysis Error. There are two ways to resolve
duplicates:
|
In Sync | The records in both datasets match. |
Orphan | A record was found in one dataset with no corresponding record in the other. |
This table shows the various sync audit statuses:
Status | Description |
---|---|
Advanced Sync Error | An error occurred during advanced processing. Advanced processing is the last stage in the sync process, when any after sync formulas that are defined in your GIS mappings are executed. |
Analysis Error | An error occurred during the analysis. |
Data Conflict | The records in the two datasets conflict. A data conflict is more
serious than a data mismatch, because the sync process can't determine which value
should take precedence. This can occur if the records in both databases have been
updated independently since the last synchronization. Your system might be configured
to resolve conflicts automatically, or it might require manual intervention. See Resolving conflicts. |
Imported | The record was imported, but advanced processing is still pending. |
Import Error | An error occurred during the import process. You can use the Sync Details tab in the Sync Audit InfoViewer to view information about the error. |
Queued For Advanced | The record is queued for advanced processing. |
Queued For Import | The record is queued for import. This could indicate that a record halted for manual intervention, or that an audit from a report-only run was advanced by the user, but the sync process hasn't acted on it yet. See the Infor Public Sector primary log for details. |
Reported | The result of the sync audit has been reported, but no action has been taken. |
Resync Conflict | An unresolvable data conflict occurred in the resynchronization after import. |
Superseded | A record synchronization was not fully processed before being superseded by a more recent process. |
Synchronized | The record was successfully imported. Synchronization is complete. |
Unanalyzed | The records have not been analyzed. |
No Action | Analysis of the records was completed, but no action was taken. |
User Ignored | The sync audit has been ignored. No further action will be taken. |
A sync audit can also have one or more associated actions, which indicate the steps taken as a result of the audit, such as creating or updating records. Use the Sync Action List tab in the Sync Audit InfoViewer to review these actions. This table shows the different types of action that you may see:
Action | Description |
---|---|
Create | A new record was created. |
New Version | A new version of a record was created. |
None | No action was taken. |
Update | A record was updated. |
User Defined | Advanced processing was completed. These means that the after sync formula for the GIS mapping was executed. |