Replicating Service data

These replication categories are used with SyteLine Service:

  • Service - Multi-Site SRO Copy
  • Service - Global Incidents
  • Service - Global Service History
  • Service - Global Units
  • Service - Global Scheduling of Shared Partners

Incidents and units

Both the Service - Global Incidents and Service - Global Units categories allow you to set up replication rules so that incidents and units that are updated in one database are synchronized to another database. When you create a replication rule for either category, set the Interval Type to Transactional.

Note: Because customer information is included on an incident, the A/R replication category must also be replicated whenever incident replication is taking place.

Incident Reason and Resolution notes are replicated with the Service - Global Incidents category. Incident notes are not replicated.

Service Console

Use the Service - Global Service History category to set up replication rules so that service information from multiple sites can be viewed together on the Service Console form. The replicated data is read-only, so system performance and business processes should determine the replication interval setting.

Service orders

The Service - Multi-Site SRO Copy category is used with the Multi-Site Service Order Copy form, which copies all lines, operations, reasons, and planned transactions of the specified SRO from one site to another. Set the replication rule interval to Transactional.

Note: The service order copy utility only works between sites that are linked and using transactional replication.

Global scheduling of shared partners

Global scheduling of shared partners can be performed by companies that have multiple back office sites but one pool of technicians (partners) who perform service work for all sites. The Service - Global Scheduling Shared Partners replication category replicates tables related to both appointments and partners. The replication rule interval should be set to Transactional.

The appointment reference is not replicated. If your company requires cross-site access to the appointment reference, you should implement scheduling by incidents and configure the system for global incidents.

The warehouse, department, work code, and misc code are not included in this replication category, because these values are optional (not required) for partner setup. If your company populates this information on the partner, you must ensure that the data exists in both sites. To do this, either implement manual data entry processes or leverage standard replication by creating a custom replication category that includes the tables to replicate.