Editing Field mapping cheatsheet for the ActiveCampaign Microsoft Dynamics integration

```mediawiki
'''Navigation:''' [[Main_Page]] > [[Apps]] > [[Integrations]] > Field mapping cheatsheet for the ActiveCampaign Microsoft Dynamics integration

= Field mapping cheatsheet for the ActiveCampaign Microsoft Dynamics integration =

== Introduction ==
The ActiveCampaign Microsoft Dynamics 365 integration allows businesses to seamlessly connect their ActiveCampaign contacts to Microsoft Dynamics 365 fields. Properly mapping these fields is essential for ensuring that data synchronizes correctly between the two platforms. '''Field mapping''' is critical in maintaining data integrity and ensuring effective communication between your CRM and marketing automation tools. Using unsupported field mapping combinations can result in records that fail to sync, potentially causing data loss or inaccuracies.

In this article, you will learn about the different field mapping combinations that are supported when setting up this integration. Understanding these combinations will help you avoid common pitfalls and ensure that your integration operates smoothly.

== How to Access ==
To access the field mapping options for the ActiveCampaign Microsoft Dynamics integration, you need to have the integration set up within your ActiveCampaign account. Once you have established the integration, you can refer to this cheatsheet for guidance on which field combinations are compatible.

== Step-by-Step Instructions ==
1. **Log into your ActiveCampaign account.**
2. Navigate to the **Apps** section in the main menu.
3. Click on **Integrations** and locate the Microsoft Dynamics 365 integration.
4. Follow the setup instructions to connect your ActiveCampaign account to Microsoft Dynamics 365.
5. Once connected, refer to the field mapping options detailed in this cheatsheet to confirm the correct fields are mapped.

== Configuration Options and Settings ==
When setting up the field mapping for ActiveCampaign and Microsoft Dynamics 365, the following combinations are supported:

=== Supported Field Mapping Combinations ===
- **ActiveCampaign field type**: 
    - Hidden 
        - *String*
        - *Whole number*
        - *Decimal*
        - *Floating point number*
        - *BigInt (very large number field)*
        - *Two option (Yes or No)*
        - *Money*
        - *Lookup (Team and User only)*
        - *Custom fields*

    - **Text** 
        - *String*
        - *Whole number*
        - *Decimal (5 numbers after decimal point)*
        - *Floating point number (10 numbers after the decimal point)*
        - *BigInt (very large number field)*
        - *Two Option (Yes or No)*
        - *Money*
        - *Lookup (Team and User only)* 
        - *Customer fields*

    - **Text area** 
        - *Textarea*

    - **Date**
        - *DateTime*

    - **Dropdown**
        - *Optionset*

    - **Radio**
        - *Optionset*

    - **Checkbox**
        - *MultiSelect*
        - *Listbox*
        - *Optionset*

    - **Score** 
        - *String*
        - *Whole number*

This mapping ensures that the data from your ActiveCampaign is accurately reflected in Microsoft Dynamics 365, allowing both platforms to operate in harmony.

== Best Practices and Tips ==
- Always ensure that you reference this cheatsheet while setting up your mapping to avoid unsupported field combinations.
- Keep your data in mind; syncing fields that contain incompatible types can lead to errors.
- Regularly review and audit your field mappings to ensure they continue to meet the needs of your business as both platforms update.
- Utilize the functionality of both ActiveCampaign and Microsoft Dynamics 365 to enhance audience targeting and contact management.

== Common Use Cases ==
1. **Lead Management**: Using the field mapping to synchronize lead fields allows for seamless tracking of potential customers from marketing to sales.
2. **Sales Reports**: Automating data flows between the two platforms ensures that the sales team has real-time insights on lead activities, enhancing decision-making processes.
3. **Customer Segmentation**: By properly mapping customer-specific fields, businesses can target messaging campaigns effectively based on data from both platforms.

== Troubleshooting ==
If you encounter issues with data not syncing:
- Check that the fields are correctly mapped as per the supported combinations outlined above.
- Ensure that the synchronization settings in both platforms are correctly configured.
- Review your integration connection; sometimes re-establishing the connection can resolve sync issues.

== Related Features ==
- For more information on integrations, refer to the [[Integrations]] section.
- Learn about how to effectively manage your contact lists in [[Contact_Lists]].

== FAQs ==
=== 1. What happens if I use an unsupported field mapping combination? ===
Unsupported combinations may prevent records from syncing, leading to data loss.

=== 2. How do I know which fields are supported for mapping? ===
Refer to the supported field mapping combinations outlined in this article.

=== 3. Can I customize fields in Microsoft Dynamics 365? ===
Yes, you can create custom fields in Microsoft Dynamics 365 as long as they are compatible with the ActiveCampaign field types.

=== 4. Will mapping fields affect my marketing campaigns? ===
Yes, accurate mapping ensures that your campaigns target the correct segments based on updated contact information.

=== 5. How often should I review my field mappings? ===
It's recommended to audit your mappings regularly, especially after major updates to either platform.

=== 6. Can I delete a mapped field later? ===
You can, but be cautious as it may disrupt data synchronization if that field is actively used.

=== 7. Is technical support available for integration issues? ===
Yes, you can contact ActiveCampaign support for assistance with integration-related problems.

By using this field mapping cheatsheet, you can ensure that your ActiveCampaign integrates effectively with Microsoft Dynamics 365, allowing for enhanced marketing efforts and streamlined operations.
```