Data Synchronization Rules & Troubleshooting

Once your data synchronization has been set up, there are a few important rules to keep in mind to ensure everything works smoothly. This guide highlights key points for both two-way and one-way synchronization, as well as rules that apply to both types, helping you avoid errors and maintain consistent data across systems.

Two-Way Synchronization

Two-way synchronization enables syncing of Groups and Personnel/Members between Personnel & Training and Operations Center.

Shared Field Requirement

The Email Address, Mobile Phone, and Work Phone fields can only be mapped with D4H Personnel & Training if they are marked as Shared in Team Manager.

If any of these fields are not marked as Shared, the system will display an error and synchronization will not work.

Phone Number Format

Before importing members from Personnel & Training or mapping phone fields, ensure that phone numbers are added in the correct format.

Phone numbers must include the country code (for example, +15551234567), otherwise they may not import or sync correctly.

Member Status Restrictions

Members with a status of Observer or Retired will not sync. To include these users, update their status to either Operational or Non-Operational and re-sync.

Alerting Configuration

If you are using D4H Alerting, you can select one phone number field to receive alerts, but multiple numbers cannot be used simultaneously.

One-Way Synchronization

One-way synchronization allows incidents to be exported from Operations Center to Incident Reporting.

Private Fields Cannot Be Mapped

Private fields can no longer be mapped to Incident Reporting. If a private field was previously mapped, Incident Management may display an Invalid Configuration error and data will not transfer correctly.

Unsupported Field Types

Additionally, field types such as Location Area, Location Map, Org Chart, Table, and Icon cannot be mapped to Incident Reporting. Any previously mapped fields of these types should be removed to restore proper synchronization.

Rules That Apply to Both Sync Types

Multi-Select (Checkbox) & Single-Select Fields

When mapping custom fields, Multi-Select (Checkbox) and Single-Select (Option Selection) fields in Incident Reporting must match the corresponding Situation Report (SitRep) fields exactly, including case sensitivity. The order of options does not need to match, but any mismatch will prevent the field from being selectable.

Relationship Fields

Relationship fields can be mapped to any Text field in Incident Reporting.

Locked Fields After Mapping

Once a field is linked to a Situation Template field, it becomes locked and cannot be modified until you deselect the mapping using the No Mapping option and save your changes.