Synchronization data
The synchronization data display the Sage X3 records in a table (tasks, calls, appointments and Outlook contacts) that are pending Outlook synchronization.
A modification, creation or deletion of one of these records mean that the mirror records in Outlook are updated.
A Sage X3 record can also be displayed in this table because it is out of phase with Outlook or because some of the information is wrong. From the synchronization data, it is thus possible to force one or several lines.
Screen management
The synchronization data table displays by default all the X3 records pending synchronization with Outlook (tasks, calls, appointments and Outlook contacts) for all users (authorized to carry out the synchronization, function GESSYP) and for all objects (TSK, CLL, BAP and COR).
When a synchronization is completed successfully, the synchronization data table is updated accordingly: the corresponding record is no longer displayed.
It remains possible to filter the results by user and/or object code.
Entry screen
From the synchronization data header, a user and an object code (TSK, CLL, BAP and COR) can be entered in order to refine the results of the search of data pending synchronization.
The actions that have caused the creation of a visible record in the table are the following:
- C: creation (of tasks, calls, appointments and Outlook contacts).
- M: modification. The data being modified has a history, it already exists in the base.
- A: deletion. The data is no longer present in the database.
- P: change of users on the record. Equivalent to a deletion on the former user.
The action corresponding to R implies that the current record has been forced.
As for statuses, three are available:
- Synchro generated
The value 0 implies that the synchronization of the event has not been started. When it is started, the line disappears from the table. - Synchro update
The value 0 implies that the event has not been updated, either because the synchronization has not been started yet or there is an anomaly between the X3 record and the Outlook record. - Outlook status
The value 1 implies that the line is valid while value 0 implies that the synchronization with Outlook has failed because of an unexpected problem.
It should be noted that if a line is directly deleted from the synchronization data table, it means that the corresponding X3 record will not be processed during the next synchronization (the modifications that may have been performed on this record will not be transferred). Nevertheless it does not mean that the X3 record will be deleted from the base.
Block number 1
| User (field FILSYDUSR) |
|
It is possible to enter the code of a user authorized to initiate an Outlook synchronization. This is used to only display those records pending synchronization and for which the user is the current user (owner). |
| Object (field FILSYDTYP) |
|
The possible object values are:
It is possible to enter one of these four codes to refine the display of those data pending Outlook synchronization. |
Grid Data
| Sequence no. (field SYDNUM) |
|
It is the internal unique number, associated with the data to be synchronized. |
| To process (field TRTLIGNE) |
|
A line is to be processed when it has been forced. |
| User (field SYDUSR) |
|
It is the code(s) for the user(s) authorized to initiate an Outlook synchronization and for whom there are records pending synchronization. |
| Type (field SYDTYP) |
|
The possible X3 object values are:
One of these four types of X3 objects corresponds to each data pending synchronization. |
| Action type (field SYDATTTYP) |
|
Types of actions available on the Sage X3 records pending Outlook synchronization (tasks, calls, appointments and contacts):
The action corresponding to R implies that the current record has been forced. |
| Key (field SYDKEY) |
|
It is the unique key of the X3 record pending Outlook synchronization. It is defined from the sequence number counter management and can be assigned either manually or automatically at the time of the creation of a new record (tasks, calls, appointments and Outlook contacts) in Sage X3 Entreprise. |
| Generation status (field SYDGEN) |
|
If the status takes the value 0, it means that the synchronization of the current event has not been started. When it is started, the line disappears from the table. |
| Update status (field SYDUPD) |
|
If the status takes the value 0, it means that the current event has not been updated, either because the synchronization has not been started yet or there is an anomaly between the X3 record and the Outlook record. |
| Outlook status (field SYDOTKSTA) |
|
If the Outlook status takes the value 1, it means that the line is valid while value 0 implies that the synchronization with Outlook has failed because of an unexpected problem. |
| Date (field SYDDAT) |
|
Date of the last update (action). |
| Time (field SYDHOU) |
|
Time of the last update (action). |
| Force |
|
The action corresponding to R implies that the current record has been forced. A data may be forced when there is an anomaly at the level of the current record, for instance; the updating of some information is out-of-phase. Forcing a line also leads to updating the To be processed flag, as well as the date and time of the last update of this forced record. |
| Force all the lines |
|
A data may be forced when there is an anomaly at the level of the current record, for instance; the updating of some information is out-of-phase. Use the action Force all the lines to perform a mass update of the To be processed flag, as well as the last update date and time for all records pending synchronization. All the lines are then forced (R action). |
| Detail |
|
Use this action, available from a table line, to access the record of the relevant record directly from the object. |
Refer to documentation