Yes, Exalate supports synchronization of custom fields across all connected platforms. You can sync custom text fields, dropdowns, checkboxes, date fields, numeric fields, and multi-select custom fields between systems with different field structures. The scripting engine gives you full control over how custom field values map and transform between platforms, accommodating naming differences, data type conversions, and value translations.
Mapping Custom Fields in Sync Scripts
Custom field synchronization requires defining the mapping in your sync scripts. For outgoing scripts, you specify which custom fields to include in the replica object and how to format their values. Incoming scripts determine how to apply custom field data from the replica to your local system, including finding the correct field by name or ID and handling cases where fields don't exist.
You have full script and operational control over your sync, ensuring sensitive custom fields can be excluded or masked while standard fields sync freely.
Syncing Custom Entities Beyond Standard Work Items
Exalate can synchronize custom entities beyond standard work items in platforms that support them:
- ServiceNow: Sync custom tables, incidents, problems, change requests, catalog tasks, and any entity available via REST API.
- Salesforce: Sync custom objects including accounts, cases, opportunities, products, and tasks.
- Azure DevOps: Sync various work item types with custom fields across Server and Cloud versions.
- Freshservice, Freshdesk, Asana: Sync platform-specific entities and custom fields tailored to each system's data model.
The platform's scripting flexibility means you're not limited to predefined entity types or standard field sets.
Helper Functions for Custom Field Operations
Helper functions simplify common custom field operations. The nodeHelper includes methods for finding custom fields by name, checking if fields exist, and handling null values safely. Organizations with extensive custom field configurations benefit from this scripting capability, eliminating the limitations of tools that only support standard field mappings.
Handling Data Type Mismatches
When synchronizing custom fields between different platforms, you handle data type mismatches through transformation logic in your scripts. For instance, you can convert a multi-select custom field in Jira to a comma-separated text field in ServiceNow, or map a custom dropdown in Azure DevOps to specific status values in another system. This flexibility ensures data flows correctly regardless of platform differences.