| Initial Synchronization Process |
- Ensure complete field mapping is created between Confirm and GIS fields when adding a new layer.
- Expect the initial sync to take time depending on asset volume.
- Allow the system to perform incremental sync every 2 minutes to keep data updated.
- Refer to the Last Update Date for the last successful sync.
|
- Do not interrupt the initial sync process, as it may cause incomplete data transfer.
- Do not assume sync failures if there is a delay; check the Last Update Date.
- Avoid frequent full resyncs, as they may cause unnecessary system load.
|
| ESRI Feature Layer Configuration |
- If a change in layer (Versioned to Non-versioned or vice versa), create a new Feature layer and enable sync for it.
|
- Do not change Feature Layers from versioned to un-versioned (or vice versa) during sync/post sync process, as this may break synchronization.
|
| Geometry Synchronization |
- Select a Geometry field in the mapping list for both Confirm and GIS to enable geometry sync.
- Ensure sync direction is correctly set in Entity field mapping.
- If sync GIS to App: Updates from ESRI should reflect in Confirm. No geometry updates should occur in ESRI from Confirm.
- If sync App to GIS: Updates from Confirm should reflect in ESRI. No geometry updates will occur in Confirm from ESRI.
- 2-way: ESRI and Confirm geometry will be in sync.
|
- Do not expect geometry to be automatically included without explicit mapping.
|
| Conflict Resolution for Sync |
- Ensure that Confirm takes precedence in conflict scenarios for two-way sync.
|
- Do not modify or remove field mappings after the sync process has started, as it may lead to data inconsistencies.
|
| Geometry Compatibility |
- Align each Feature Group in Confirm with a single geometry type (point, line, or polygon) to prevent sync issues with ESRI.
- If a feature group contains multiple geometry types, split them into separate groups before syncing.
|
- Do not attempt to sync a feature group with multiple geometry types to a single ESRI layer.
- Do not encourage asset geometry deletion, as it may lead to data integrity issues.
|
| Feature Attribute Editability & Sync Direction |
- If a Feature attribute in Confirm is not editable, understand that sync direction will be one-way (App to GIS) by default.
- If a Feature attribute in ESRI is not editable, understand that sync direction will be one-way (GIS to App) by default.
|
- Do not assume that all attributes will allow two-way sync.
|
| End Date Behaviour |
- Confirm does not support setting an End Date during new asset creation. Newly created assets won’t have one by default.
- If sync direction for End Date is 2-way or App to GIS, ESRI will default End Date to 01-01-3000, which Confirm interprets as default for active records.
- Ensure End Date is always greater than the Start Date for asset records.
|
|
| Field Mapping & Data Types |
- Verify & add all field mappings before starting sync to avoid inconsistencies.
- While mapping fields on GIS Field mapping screen, only choose fields of the same data type.
- Verify the data type of fields before mapping to prevent errors.
|
- Do not map fields of incompatible data types (e.g., Integer to String).
|
| Field Mapping & Data Types |
- Verify & add all field mappings before starting sync to avoid inconsistencies.
- While mapping fields on GIS Field mapping screen, only choose fields of the same data type.
- Verify the data type of fields before mapping to prevent errors.
|
- Do not map fields of incompatible data types (e.g., Integer to String).
|
| Bulk Update for Picklist Attributes in ESRI |
- Use code values in SQL queries when performing bulk updates on picklist fields.
- When manually updating, select appropriate labels that exist in both systems.
|
- Do not use incorrect formats during bulk updates, as it may cause picklist errors.
|
| Picklist Mapping in ESRI |
- Create picklists in ESRI with both a key (label) and value (code).
|
- Do not manually enter inconsistent picklist values—it may cause mapping issues.
|
| CAID Handling |
- Always provide a CAID in ESRI when syncing data to Confirm.
- Ensure CAIDs are consistent between Confirm and ESRI.
- Be aware that new CAIDs will be created in Confirm if values differ.
- Ensure CAIDs are uniquely assigned in ESRI.
- Understand that if no CAID is given, Confirm generates one, but ESRI will not display it.
|
- Do not alter CAIDs on either system after sync.
- Do not leave CAID blank in ESRI when pushing data to Confirm.
- Avoid editing CAIDs in both systems to maintain data integrity.
|
| Feature Field Terminology |
- Use standard Confirm terminology when mapping fields in entity field mapping.
|
- Do not use inconsistent terminology—only standard names are valid in mapping.
|
| Feature Group Sync |
- Understand that sync occurs at the Feature Group level, including all child Feature Type Codes (FTCs).
|
- Do not assume only specific FTCs will sync independently.
|
| Time Zone Settings |
- Ensure the tenant has a time zone setting in Confirm (e.g., America/New_York).
- All date-type fields will convert according to tenant’s time zone.
|
- Do not leave time zone settings blank—it will interrupt sync.
|
| Feature Configuration Considerations |
- Ensure seed numbers for FTC, CAID, and Feature Group are populated to avoid sync failures.
|
- Do not allow seed number ranges to exhaust—sync will fail.
- Do not include spaces in prefix, suffix, or middle of FTC, CAID, or Site Code—it interrupts sync.
|
| Asset Deletion from ESRI |
- Follow proper asset lifecycle practice by updating End Date instead of deleting.
|
- Do not delete assets directly—it may compromise data integrity.
|
| Progress Bar Behaviour |
- Understand that if no data exists in either system, progress bar will still show.
- Progress bar is visible only during initial sync.
- Ensure updates exist before expecting "Last Updated" date to change.
|
- Do not assume the progress bar is stuck—verify data presence in both systems.
- Do not expect "Last Updated" to change if no updates occurred.
|
| Attribute Field Length |
- Configure ESRI field length during field creation to match or exceed Confirm's 2000 character limit for strings.
- Ensure integer/double values from ESRI meet Confirm field limits.
- Validate data size compatibility before syncing.
- Ensure synced data truncates correctly per system limits.
|
- Do not send numeric values exceeding Confirm’s supported limit—may cause Arithmetic Overflow errors.
|
| Invalid HTML Tags |
- Use plain text for all text attributes.
|
- Avoid using angle brackets (< or >) or HTML tags—they may interrupt sync.
|