Sync History Detail View

Use the Sync History Detail view to see detailed information about a synchronization history item. Synchronization history items are associated with jobs run between Infor CRM and an external integration. Sync history information shows what records were synchronized and when they were synchronized and can provide information for troubleshooting synchronization problems.

How Do I?

Open the Sync History Detail viewClosed
  • On the Navigation Bar, click Integration, and then click Sync History to open the Sync History List view. If necessary, use the Lookup to locate a history item, and then click the log name.

Use the Lookup to search for records

Switch to the List viewClosed
  • On the toolbar click the List ViewClosed button, or click the current group tab.

View a group

information boxes 

The information boxes contain the primary information about the synchronization item.

Box Description
Date Time Stamp The date and time the synchronization job began.
Sync Job The sync job that included the sync history item.
Error Sequence Displays a number sequence if multiple message and results are linked together from one job. For example, if one sync job produces 3 errors, you will see an entry for errors 1, 2, and 3.
Severity

The severity of the diagnosis entry. Possible values are:

  • Info - No special attention is required.
  • Warning - The operation is not prevented from succeeding but may require attention.
  • Transient - The operation failed but may succeed later in the same condition.
  • Error - The operation failed and should be modified before resubmitting.
  • Fatal - The operation contains a fatal error and must be modified before resubmitting. Other operations may also fail.
Resource Type The type of resource synchronized between applications.
Entity Type The record type that changed.
Payload Path The XPath expression that refers to the payload element responsible for the error. This element is only used when the error is related to a specific piece of data being sent to the service provider. For example, when updating a resource or submitting a service request.
Application The application that received the change.
Sent By The integration used to send the change.
Message Id/Code The application specific diagnosis code or message ID.
Diagnosis Code

The SData diagnosis code. The following are valid diagnosis codes:

  • BadUrlSyntax - The URL syntax is invalid. 
  • BadQueryParameter - The Query Parameter is invalid.
  • ApplicationNotFound - The application does not exist.
  • ApplicationUnavailable - The application exists but is not available.
  • DatasetNotFound - The dataset does not exist.
  • DatasetUnavailable - The dataset exists but is not available.
  • ContractNotFound - The contract does not exist.
  • ResourceKindNotFound - The resource kind does not exist.
  • BadWhereSyntax - The where condition has an invalid syntax.
  • ApplicationDiagnosis - The application specific diagnosis. The detail displays in the Application Code column.

Back office integration diagnosis codes

  • -1 - No active Back Office found for specified Logical ID
  • 0 - Data waiting to be processed
  • 1 - Data successfully processed
  • 9 - missing or invalid data content
  • 999 - Run time exception error
Status

The status of the current synchronization cycle. Values include:

  • OK - Data was sent successfully
  • Internal Server Error - An error occurred. Please see the Error Message field for additional information.
  • Not Modified - Data was not modified due to conflict resolution.
  • Forbidden - The action could not be completed.
  • Not Found - The server has not found anything matching the Request-URI.

Back office integration status values:

  • Failed to Process - Invalid or missing data content
  • Successfully Processed - The data was successfully synchronized.
  • Configuration Error - There is not an active Back Office for the specified Logical ID.
Entity Value The display value of the related record ID.
Error Message The complete error message.
Stack Trace The list of the classes and methods that were accessed prior to the error. Information only displays if there was an error during synchronization.
Payload Detail

The complete payload XML. This information is saved only when there is an error applying it.

 

 

What's New in this Release

 

For a list of new features, see the What's New In This Release topic.

Other Resources

 

Getting Started with Infor CRM Web Client

Infor CRM Quick Reference for the Web User

Getting Started with Infor CRM Back Office Extension

Contact us:

This documentation was developed by Infor CRM User Assistance. For content revisions, questions, or comments, contact the Infor CRM writers at documentation@infor.com.