Skip to main content

How do I Configure and Manage Organization Field Mapping(s) for Salesforce Integration?

Azavista Support
Updated

Configuring and Managing Organization Field Mapping(s)

Overview

This article explains how administrators can configure Organization field mappings between Azavista and Salesforce. It covers how to create mappings for different field types, define sync directions (Inbound, Outbound, and Bidirectional), and validate synchronization using CRUD operations.

By following this guide, admins can ensure accurate and reliable data exchange between Salesforce and Azavista.

Step-by-Step Approach

1. Access Organization Mapping within Salesforce Integration

  • From the General Dashboard, go to Integrations.
  • Open the active Salesforce Integration.
  • Click the Organization Mapping tab.

2. Steps to Add and Manage Field Mapping

Add Field Mapping

  • Click Add button.
  • Select the Azavista Organization Field.
  • Select the corresponding Target CRM Field.
  • Ensure both fields have the same data type.
  • Save the mapping.

Manage Sync Direction

  • Go to More Options (⋮), click Sync Direction.
  • Choose the required Sync Direction:
    • Inbound (Salesforce → Azavista)
    • Outbound (Azavista → Salesforce)
    • Bidirectional (Two-Way Sync)

    Understanding Sync Direction

    1. Sync from Azavista to Salesforce (AZ → SF)

    When data needs to be synchronized from Azavista to Salesforce, only the configuration inside Azavista matters.

    • The Salesforce Integration must be properly configured in Azavista.
    • Global Processes and Actions must allow sending data to Salesforce.
    • No additional configuration is required inside the Salesforce package for this direction.

    2. Sync from Salesforce to Azavista (SF → AZ)

    When data needs to be synchronized from Salesforce to Azavista, both systems must be configured correctly.

    • The Azavista Package inside Salesforce must be configured with the correct Sync Status and Endpoint.
    • The Salesforce Integration inside Azavista must allow incoming synchronization.
    • Required permissions and object settings must be enabled in both systems.

    Syncing Deletions

    Currently, synchronization of deleted records between Azavista and Salesforce is not supported.

    Manage Attribute Mapping

    • Go to More Options (⋮),click Manage Attribute Mapping.

    Note: Manage Attribute Mapping option is only applicable for Lookup, Select and Multi-Select field types.

    Delete Field Mapping

    • Go to More Options (⋮), click Delete.

    3. Validate Synchronization (CRUD)

    After creating a mapping, validate it using CRUD operations:

    • Create: Add a new record in the source system and verify it appears in the target.
    • Read: Check if synced data displays correctly.
    • Update: Modify the field value and confirm it syncs.
    • Delete: Remove a record (if supported) and verify sync behavior.

    Inbound Sync Validation

    • From the Azavista General Dashboard, go to CRM.
    • Go to Organizations and edit an Organization.
    • Edit the mapped field value.
    • Go to the Salesforce dashboard and open the selected Organization.
    • Validate the mapped field value.

    Outbound Sync Validation

    • From the Salesforce dashboard, go to Organizations.
    • Edit the selected Organization.
    • Edit the mapped field.
    • Go to Azavista General Dashboard, select CRM.
    • Go to the edited Organization.
    • Validate the mapped field value.

    Bidirectional Sync Validation

    • Edit the mapped field in Azavista.
    • Validate the update in Salesforce.
    • Edit the mapped field in Salesforce.
    • Validate the update in Azavista.

    Note: For both-side sync, always select the Bidirectional sync direction.

    4. Field Mapping by Type

    Boolean Field Mapping

    • Inbound: Create mapping, set Inbound, validate in Salesforce.
    • Outbound: Create mapping, set Outbound, validate in Azavista.
    • Bidirectional: Create mapping, set Bidirectional, validate in both systems.

    Text Field Mapping

    • Inbound: Create mapping, set Inbound, validate in Salesforce.
    • Outbound: Create mapping, set Outbound, validate in Azavista.
    • Bidirectional: Create mapping, set Bidirectional, validate in both systems.

    Date-Time Field Mapping

    • Inbound: Create mapping, set Inbound, validate in Salesforce.
    • Outbound: Create mapping, set Outbound, validate in Azavista.
    • Bidirectional: Create mapping, set Bidirectional, validate in both systems.

    Email Field Mapping

    • Inbound: Create mapping, set Inbound, validate in Salesforce.
    • Outbound: Create mapping, set Outbound, validate in Azavista.
    • Bidirectional: Create mapping, set Bidirectional, validate in both systems.

    Lookup Field Mapping

    • Inbound: Create mapping, set Inbound, validate in Salesforce.
    • Outbound: Create mapping, set Outbound, validate in Azavista.
    • Bidirectional: Create mapping, set Bidirectional, validate in both systems.

    Date Field Mapping

    • Inbound: Create mapping, set Inbound, validate in Salesforce.
    • Outbound: Create mapping, set Outbound, validate in Azavista.
    • Bidirectional: Create mapping, set Bidirectional, validate in both systems.

    Select Field Mapping

    • Inbound: Create mapping, set Inbound, validate in Salesforce.
    • Outbound: Create mapping, set Outbound, validate in Azavista.
    • Bidirectional: Create mapping, set Bidirectional, validate in both systems.

    Multi-Select Field Mapping

    • Inbound: Create mapping, set Inbound, validate in Salesforce.
    • Outbound: Create mapping, set Outbound, validate in Azavista.
    • Bidirectional: Create mapping, set Bidirectional, validate in both systems.

    Integer Field Mapping

    • Inbound: Create mapping, set Inbound, validate in Salesforce.
    • Outbound: Create mapping, set Outbound, validate in Azavista.
    • Bidirectional: Create mapping, set Bidirectional, validate in both systems.

    Number (Decimal) Field Mapping

    • Inbound: Create mapping, set Inbound, validate in Salesforce.
    • Outbound: Create mapping, set Outbound, validate in Azavista.
    • Bidirectional: Create mapping, set Bidirectional, validate in both systems.

    Time Field Mapping

    • Inbound: Create mapping, set Inbound, validate in Salesforce.
    • Outbound: Create mapping, set Outbound, validate in Azavista.
    • Bidirectional: Create mapping, set Bidirectional, validate in both systems.

    URL Field Mapping

    • Inbound: Create mapping, set Inbound, validate in Salesforce.
    • Outbound: Create mapping, set Outbound, validate in Azavista.
    • Bidirectional: Create mapping, set Bidirectional, validate in both systems.

    Travel DateTime Field Mapping

    • Inbound: Create mapping, set Inbound, validate in Salesforce.
    • Outbound: Create mapping, set Outbound, validate in Azavista.
    • Bidirectional: Create mapping, set Bidirectional, validate in both systems.

    Best Practices

    • Always match field data types between Azavista and Salesforce.
    • Test mappings in a staging environment before production use.
    • Validate all mappings using CRUD operations.
    • Avoid duplicate mappings for the same fields.
    • Review sync logs regularly.
    • Monitor timezone and format settings for date and time fields.

    Note: Image, Document, Rating, and Opinion Scale field types are not supported for synchronization.

Related to

Related articles