The functions are the following:
The synchronization process is used to:
This documents presents:
The setup information required to establish the synchronization and general principles and conditions for forcing the synchronization are available in the documentation: Synchronization Sage X3 - Outlook: installation.
When the synchronization is launched, only the Outlook tasks tagged as "private" will not be generated as Sage X3 tasks.
Notes:
The data concerning a Sage X3 task are synchronized with an Outlook task under certain conditions:
In the Outlook task, in order to open the following elements directly in the browser, hyperlinks are present on each element:
Sage X3 fields | Outlook fields | Sage X3 | Outlook | Comments |
UPDDAT | LastModificationTime | --- | X | This value is only recovered if there is a conflict (the same recording is modified both in Sage X3 and Outlook). |
TSKCRM | Companies | X | X | If the information is not available, but the Outlook contact is attached to a BP in Sage X3, the BP reference is recovered via the contact. |
HOUTIMSPG | ActualWork | X | X | Two fields in Sage X3: one in hours, the other one in minutes. |
TSKDON | Complete | --- | X | If "Completed" in Outlook, then "Completed" in Sage X3. |
TSKDON | Status | X | --- | If "Completed" in Sage X3: "Completed" in Outlook. |
TSKSTR | StartDate | X | X |
|
TSKDAT | DueDate | X | X |
|
FULOBJ | Subject | X | X | Note that this field is limited to 255 characters in Outlook. |
FULRPO | Body | X | X | During a Sage X3 to Outlook synchronization, the information entered in this field is preceded with details on the task if available: see note (1) below. |
TSKREP |
| --- | --- | This section is not synchronized. |
SALFCY |
| --- | --- | This section is not synchronized. |
TSKCOR | Lk_1_CtAdxId | X | X | During an Outlook => Sage X3 synchronization, if the Outlook contact references a contact (TSKCCN), this contact is automatically recovered. Same behavior when the Outlook contact is attached to a BP (TSKCMP). |
| Lk_1_Name | X | ---- | Name and surname of the Outlook contact under the format: |
TSKDAT | AdxTaskDateTime | X | --- |
|
(1) More information on the call:
Category: [F:TSK]TSKTYP ([F:ADI]LNGDES)
Priority level: [F:TSK]TSKPIOLEV ([F:ADI]LNGDES)
Inform the delay after [F:TSK]TSKDEL days
Example:
Category: D1 (Reminder)
Priority level: B1 (Normal)
Inform the delay after 2 days
(2) As a reminder, the contact management function is used within the framework of the synchronization function of Sage X3 with Outlook.
Contacts can be defined in Outlook independently from Sage X3. This means they are not part of the contacts list. When an Outlook synchronization is started, the Outlook contact table is used to store temporarily the information coming from these Outlook contacts since they do not exist as contacts in the database yet. Further on, a contact generation function, accessible from the tool bar of the GESCOR - Outlook Contactsfunction, is used to combine an Outlook contact with a contact.
The sine qua non conditions, allowing the automatic creation of contacts and their update following an Outlook synchronisation, are:
The appointments resulting from Outlook are classified into two categories:
From an Outlook point of view, the first category concerns the appointments (appointment) and the second category, the meetings (meeting).
From an X3 point of view, the managed processes are the following:
In general, when a synchronization of Outlook appointments is started, the table of the Sage X3 appointments is updated in parallel (creation or modification of the concerned recordings) and stores the information resulting from these Outlook appointments. Similarly, when a synchronization of Sage X3 appointments is started, the Outlook appointments are then created or modified.
Only the "private" Outlook appointments will not be generated as Sage X3 appointments once the synchronization will have started.
Notes:
The data concerning a Sage X3 appointment are synchronized with an Outlook appointment under certain conditions:
In the Outlook appointment, in order to open the following elements directly in the browser, hyperlinks are present on each element:
Fields | Fields | Sage X3 | Outlook
| Comments |
UPDDAT | LastModificationTime | --- | X | This value is only recovered if there is a conflict (the same recording is modified both in Sage X3 and Outlook). |
APTCOR_x | Lk_x_CtAdxId | X | X | During an Outlook => Sage X3 synchronization, if the Outlook contact references a contact (TSKCCN), this contact is automatically recuperated. Same behavior when the Outlook contact is attached to a BP (TSKCMP). |
| Lk_x_Name | X | --- | Name and surname of the Outlook contact under the format: |
ATPADDCMT | Location | X | X |
|
FULDAY | AllDayEvent | X | X |
|
APTDUR | Duration | X | X |
|
APTDAT | Start | X | X | Two fields in Sage X3: one in hours, the other one in minutes. |
APTDATEND | End | X | X | Two fields in Sage X3: one in hours, the other one in minutes. |
FULOBJ | Subject | X | X | Note that this field is limited to 255 characters in Outlook. |
FULRPO | Body | X | X | During a Sage X3 => Outlook synchronization, the information entered in this field is preceded with details on the appointment if available: see notes (2) and (3) below. |
ATPREPMNA |
| --- | X |
|
| AdxRef | X | --- | Technical section used to know if the user that performs the synchronization is the appointment organizer or an attendee. |
APTTYP |
| --- | --- | This section is not synchronized. |
(1) As a reminder, the contact management function is used within the framework of the synchronization function of Sage X3 with Outlook.
Contacts can be defined in Outlook independently from Sage X3. This means they are not part of the contacts list. When an Outlook synchronization is started, the Outlook contact table is used to store temporarily the information coming from these Outlook contacts since they do not exist as contacts in the database yet. Further on, a contact generation function, accessible from the tool bar of the GESCOR - Outlook Contacts function, is used to combine an Outlook contact with a contact.
The sine qua non conditions, allowing the automatic creation of contacts and their update following an Outlook synchronisation, are:
(2) If the connected user is the organizer of the appointment:
Appointment organized by: [F:BPR]BPRNAM
Contacts to visit (1 to n)
mess([F:AIN]TTL,941,1) [F:AIN]FNA [F:AIN]LNA
Consultants (1 à n)
[F:BPR]BPRNAM
Location of the appointment: mess([F:BAP]APTPLC,955,1)
[F:BAP]ATPADDCMT
[F:BAP]APTADD(0)
[F:BAP]APTADD(1)
[F:BAP]APTADD(2)
[F:BAP]APTZIP [F:BAP]APTCTY
[F:BAP]APTSAT
Telephone: [F:BAP]APTTEL
Category: [F:BAP]APTTYP ([F:ADI]LNGDES)
Example:
Appointment organized by: Paul Durand
Persons to visit
Consultants
Pierre Dupont
Location of the appointment: On the customer's premises
6591 Irvine Center Dr
926182129 Irvine
US
CA
Category: B1 (customer visit)
(3) If the connected user is not the organizer of the appointment:
Location of the appointment: mess([F:BAP]APTPLC,955,1)
[F:BAP]ATPADDCMT
[F:BAP]APTADD(0)
[F:BAP]APTADD(1)
[F:BAP]APTADD(2)
[F:BAP]APTZIP [F:BAP]APTCTY
[F:BAP]APTSAT
Telephone: [F:BAP]APTTEL
Category: [F:BAP]APTTYP ([F:ADI]LNGDES)
Example:
Location of the appointment: On the customer's premises
6591 Irvine Center Dr
926182129 Irvine
US
CA
Category: B1 (customer visit)
The "Call" notion does not exist in Outlook, so calls are not managed as such in Outlook and are considered as tasks during the synchronization.
The synchronization of calls from Sage X3 to Outlook requires the creation of singular tasks in Outlook. This way, Sage X3 calls are managed the same way as Sage X3 tasks: they are dealt with in Outlook's tasks management tool of the current operator.
Only the Adxld (counter) ID changes in order to differentiate between Sage X3 calls and tasks in Outlook:
This way, the creation of a call is done first from Sage X3. It is then synchronized and generated in Outlook's tasks management tool. At this level, the 'task call' can be modified, then synchronized again and, as a consequence, it has an impact on the Sage X3 initial record.
Notes:
The data concerning a Sage X3 call are synchronized with an Outlook task under certain conditions:
In the Outlook call, in order to open the following elements directly in the browser, hyperlinks are present on each element:
Fields | Fields | Sage X3 | Outlook | Comments |
CLLCOR | Lk_1_CtAdxId | X | X | During an Outlook => Sage X3 synchronization, if the Outlook contact references a contact (CLLCCN), this contact is automatically recuperated. Same behavior when the Outlook contact is attached to a BP (CLLCMP). |
| Lk_1_Name | X | --- | Name and surname of the Outlook contact under the format: |
CLLCMP | Companies | X | X | If the information is not available, but in Sage X3, the Outlook contact is attached to a BP, the BP reference is recovered via the contact. |
CLLDUR | ActualWork | X | X |
|
CLLDON | Complete | --- | X |
|
CLLDON | Status | X | --- | If "Completed" in Sage X3: "Completed" in Outlook. |
CLLDATX | AdxTaskDateTime | X | --- |
|
CLLDAT | StartDate | X | X |
|
CLLDATX | DueDate | X | --- |
|
FULOBJ | Subject | X | X | Note that this field is limited to 255 characters in Outlook. |
FULRPO | Body | X | X | During a Sage X3 => Outlook synchronization, the information entered in this field is preceded with details on the task if available: |
CLLREP |
| --- | --- | This section is not synchronized. |
SALFCY |
| --- | --- | This section is not synchronized. |
(1) More information on the call:
Qualification:
Category: [F:CLL]CLLCAT ([F:ADI]LNGDES)
Priority level: [F:CLL]CLLPIOLEV ([F:ADI]LNGDES)
Information:
Direct line: [F:CLL]CLLETS
Mobile phone: [F:CLL]CLLMOB
E-mail: [F:CLL]CLLEML
Example:
Qualification:
Category: E1 (Customer follow-up)
Priority level: B1 (Making an appointment)
Information:
Direct line: 0450112233
Mobile phone: 0606060606
E-mail: florent.dupont@sage.fr
Fields | Fields | Sage X3 | Outlook | Comments |
CPYEML | Email1Address | X | X |
|
HOMEML | HOMEML | X | X |
|
CPYZIP | BusinessAddressPostalCode | X | X |
|
HOMZIP | HomeAddressPostalCode | X | X |
|
CPYSAT | BusinessAddressState | X | X |
|
HOMSAT | HomeAddressState | X | X |
|
LAN | Language | X | X |
|
LNA | LastName | X | X |
|
CPYCRY | BusinessAddressCountry | X | X |
|
HOMCRY | HomeAddressCountry | X | X |
|
FNA | FirstName | X | X |
|
CPYADD(0) | BusinessAddressStreet | X | X |
|
HOMADD(0) | HomeAddressStreet | X | X |
|
BPRNUM | CompanyName | X | X |
|
CPYFAX | BusinessFaxNumber | X | X |
|
HOMFAX | HomeFaxNumber | X | X |
|
CPYTEL | BusinessTelephoneNumber | X | X |
|
HOMTEL | HomeTelephoneNumber | X | X |
|
CPYMOB | MobileTelephoneNumber | X | X |
|
FNCLIB | JobTitle | X | X |
|
TTR | Title | X | X |
|
CPYCTY | BusinessAddressCity | X | X |
|
HOMCTY | HomeAddressCity | X | X |
|
CRCCLOB | Body | X | X |
|
COPREP |
| --- | --- | This section is not synchronized. |
LNA | FileAs | X | --- | Data formatted as follows: |