
This document explains the WeGive Salesforce integration, covering setup, configuration, debugging, and the data synchronization process.
WeGive pulls in data from various sources, including in-person payments, checks, stock donations, and more, ensuring a comprehensive view of donor activity. This positions WeGive as a Customer Data Platform (CDP).
It's designed for Salesforce administrators who need to understand, configure, and troubleshoot the integration who are also admin users of a WeGive account.
To get started with the WeGive Salesforce integration, you will need:
The integration relies on the OAuth username-password flow. This flow requires that you provide WeGive with the Salesforce connected app's client ID and client secret, and a Salesforce system administrator username and password. This allows WeGive to securely access and interact with your Salesforce data.
For Salesforce instances created after Summer 2023, the OAuth username-password flow must be explicitly enabled. Failure to do so will prevent the integration from connecting.
The connection will only be successful if both the WeGive and Salesforce instances are the same type (production or sandbox). You cannot connect a production WeGive account to a sandbox Salesforce instance, or vice versa.
The setup process assumes you have already enabled the Salesforce integration within your WeGive account, granting you access to the configuration settings.
Once the integration is enabled in WeGive, follow these steps to set it up in Salesforce:
1. Create a Connected App in Salesforce:
2. Access and Copy the Consumer Key and Secret Key:
3. Configure IP Relaxation Settings:
4. Add WeGive API as a Remote Site:
5. Enable Username-Password Flow for Instances Created After Summer 2023:
6. Configure Field-Level Security in Salesforce:
7. Input Salesforce Details in WeGive:
The WeGive Salesforce integration syncs every 15 minutes to pull data from Salesforce. Pushes from WeGive to Salesforce happen with a 5-minute delay for optimization. You can also manually trigger a sync from the integration settings page in WeGive.
Remember to refer to the help article provided by WeGive for detailed guidance throughout the setup process.
Key Points to Remember:
Here are some key elements and functionalities you can expect to find on this screen:
The exact appearance and functionalities of the WeGive Salesforce integration screen may vary depending on the specific version of WeGive you are using.
Setting up object and field mapping in the WeGive Salesforce integration involves configuring how data from specific objects and fields in WeGive corresponds to objects and fields in Salesforce. This mapping ensures that information is transferred accurately and consistently between the two platforms.
In WeGive, the mapping is primarily managed through the “Mapping Rules” section of the Salesforce integration settings. This section provides a visual interface to define the relationships between WeGive objects and fields and their counterparts in Salesforce. You can add new mappings, modify existing ones, or disable mappings that you don't need.
Mapping Rules Customization Options in WeGive:
Understanding Object Relationships:
You need to understand the default object relationships between WeGive and Salesforce. For example:
The integration syncs based on payments made in Salesforce. It will not function unless payments are being utilized within Salesforce.
Field-Level Security in Salesforce:
While WeGive handles the mapping rules, you need to ensure proper field-level security is configured within Salesforce. Even if your integration user is a system administrator, hidden fields in Salesforce will cause sync errors. To adjust field-level permissions:
Custom Objects in Salesforce:
Key Considerations:
By carefully configuring the object and field mapping in WeGive and Salesforce, and paying attention to field-level security settings in Salesforce, you can ensure smooth and accurate data synchronization between the two platforms, enabling a seamless flow of information between your fundraising and donor management systems.
Here are the default object mappings between WeGive and Salesforce:
WeGive
Salesforce
Donor (Individual)
Contact
Donor (Company)
Account
Household
Account (with Record Type = "Household Account")
Campaign
Campaign
Donation
Opportunity
Payment
Payment (npe01__OppPayment__c)
Recurring Plan
Recurring Donation (npe03__Recurring_Donation__c)
Designation
GAU (General Accounting Unit)
Pledge
Pledge_Plan__c (custom object)
Payout
Custom Object (details not specified)
Key Points about the Object Mappings:
It's crucial to understand that these are the default mappings. WeGive offers extensive customization options through Mapping Rules, allowing organizations to change how fields are mapped or disable the mapping entirely.
In addition to the direct object mappings, the integration considers related objects to ensure data consistency and maintain relationships. For instance, when syncing a Donation, the integration will take into account associated data like the Donor, Campaign, Recurring Plan, and Pledge, updating corresponding fields in Salesforce accordingly. This allows for a more comprehensive and accurate representation of giving data across both platforms.
The WeGive-Salesforce integration creates a bidirectional link between Contacts in Salesforce and individual donors in WeGive. If a donor doesn’t exist in Salesforce, the integration will create a new Contact and Account for that donor. When a donor already exists in Salesforce, the integration syncs the existing data with WeGive.
WeGive prioritizes syncing on emails. If a Salesforce instance has Contacts without emails, they may not be synced. By default, the integration is configured to only sync Contacts with emails, ensuring that the primary means of communication is consistently maintained. However, you can customize this setting in WeGive to sync all Contacts, regardless of whether they have an email address.
WeGive pulls data from Salesforce every 15 minutes, including updates to Contacts. Pushes to Salesforce from WeGive occur on a 5-minute delay.
Here is a list of fields that are mapped by default between WeGive and Salesforce for individual donors. These mappings can be customized in the WeGive platform:
WeGive Field → Salesforce Field
Note:
In addition to these fields, WeGive syncs other related data, such as the donor’s household, donation history, and recurring donation information.
When importing recurring donations from Salesforce, the relationship between the recurring donation and the donor can be controlled by how the data is set up in Salesforce. To attribute a recurring donation to a Company (Account) in WeGive, ensure the record in Salesforce only has an Account ID associated with it. If it has both a Contact ID and an Account ID, the recurring donation will be related to the primary Contact instead.
To ensure a successful and efficient sync:
In the WeGive-Salesforce integration, Salesforce Accounts represent two types of supporters in WeGive: Companies and Households.
It's important to understand how this object relationship interacts with the integration between individual donors in WeGive and Contacts in Salesforce:
Default Field Mappings for Accounts:
The following fields are mapped by default between WeGive and Salesforce for Companies and Households. You can customize these mappings in WeGive:
WeGive Field → Salesforce Field
Key Considerations:
By understanding the object relationships and field mappings for Accounts, you can ensure the integration effectively syncs Company and Household data between WeGive and Salesforce. Regularly reviewing the integration logs helps identify and address any inconsistencies or errors, ensuring data integrity and a comprehensive view of your supporters.
The WeGive-Salesforce integration establishes a bidirectional link between Campaigns in Salesforce and Campaigns in WeGive. This synchronization allows for the seamless flow of campaign data between the two platforms, ensuring consistency and facilitating comprehensive reporting and analysis.
Default Field Mappings:
The following fields are mapped by default between WeGive and Salesforce for campaigns. You can customize these mappings within the WeGive platform:
Note:
Use Cases:
Key Considerations:
By effectively leveraging the campaign integration, organizations can streamline their fundraising efforts, enhance reporting capabilities, and gain a more comprehensive understanding of their campaigns' impact.
The WeGive-Salesforce integration connects General Accounting Units (GAUs) in Salesforce with Designations in WeGive. This bi-directional synchronization ensures consistent data flow between the systems, streamlining fund management and reporting.
How This Integration is Used:
Additional Insights:
To gain a deeper understanding of the specific fields mapped for GAUs and Designations, you would need to consult the WeGive API documentation or reach out to WeGive support for a detailed list of available mappings. Regularly monitoring the integration logs in WeGive will also help identify and address any inconsistencies or errors during the synchronization process, ensuring data integrity.
The WeGive-Salesforce integration centers around payments, using Opportunities and Payments in Salesforce to represent Transactions in WeGive. It's important to note that WeGive syncs on the Payment level, not the Opportunity level. So, a single Opportunity in Salesforce with multiple Payments will be reflected as multiple, individual Transactions in WeGive.
Here's a breakdown of the key objects and field mappings:
1. Salesforce Opportunities:
2. Salesforce Payments (npe01__OppPayment__c):
Default Field Mappings for Transactions and Payments:
The sources don't provide a comprehensive list of all the default mappings. However, based on the available code snippets and context, here are some of the key fields that are likely mapped:
Associated Objects and Fields:
In addition to the fields listed above, the integration considers data from various associated objects to provide context and maintain relationships:
Important Considerations:
By understanding the relationships between Opportunities, Payments, and Transactions, as well as the default field mappings, you can ensure a smooth and accurate flow of payment data between WeGive and Salesforce. As always, diligently reviewing the integration logs in WeGive will help you identify and address any inconsistencies, ensuring your payment data is reliable and reflects your organization's financial activity.
The WeGive-Salesforce integration links Recurring Donations in Salesforce with Recurring Plans in WeGive, ensuring that recurring giving information is synchronized across both platforms. This synchronization facilitates a unified view of recurring donor activity and streamlines management.
While a complete list of default field mappings is not explicitly provided in the sources, the code excerpts and explanations offer insights into key fields and relationships that are considered.
Key Points to Understand:
Default Field Mappings (based on code and context):
Associated Objects and Considerations:
Using the Recurring Gift Integration Effectively:
The integration between recurring gifts in Salesforce and recurring plans in WeGive provides several benefits:
For a complete and up-to-date list of all default field mappings, you should consult the WeGive API documentation. In addition, regularly monitoring integration logs in WeGive can help identify and address any discrepancies that might arise, ensuring the accuracy and reliability of your recurring giving data.
The WeGive-Salesforce integration handles Pledges by utilizing a custom object in Salesforce named Pledge_Plan__c. This custom object is necessary because Salesforce does not have a native object specifically for pledges. The integration allows for the synchronization of pledge data between the two systems, ensuring that pledge information is consistently updated.
Here's a breakdown of the key aspects of the Pledge integration:
Default Field Mappings (based on the code and context):
Here are some of the fields that are likely mapped by default between WeGive's Pledge object and Salesforce's Pledge_Plan__c custom object:
WeGive Pledge Field
Salesforce Pledge_Plan__c Field
amount
Amount__c
donor.salesforce_id
Contact__c
donor.salesforce_account_id
Account__c
campaign.salesforce_id
Campaign__c
start_date
Date_Established__c
end_date
End_Date__c
fund.salesforce_id
GAU_Allocation__c
installment_frequency
Installment_Period__c
Associated Objects and Considerations:
The integration also considers various associated objects and fields to provide a complete picture of the pledge and its relationships:
While this information provides a good overview of the Pledge integration, it's important to note that a complete and up-to-date list of all default field mappings should be obtained from the WeGive API documentation. Regularly reviewing the WeGive integration logs is also highly recommended to identify and resolve any potential data discrepancies. This ensures that your pledge data is accurate and reflects the current status of pledges made through your organization.
Request information from your WeGive account manager.
Request information from your WeGive account manager.
Request information from your WeGive account manager.
Request information from your WeGive account manager.
Custom Object Mapping Process:
Currently, there is no dedicated user interface in WeGive for mapping custom objects, but WeGive is actively developing such a UI to streamline the process. Custom objects are mapped via request. Custom fields are mapped via the UI.
Steps:
Flexibility of Custom Object Mapping:
Charlie emphasizes that WeGive doesn't require a strict adherence to specific object structures in Salesforce. The system is designed to be flexible, as long as the custom object in Salesforce:
Example (GAU/Funds):
Charlie highlights an existing example of custom object mapping with GAUs (General Accounting Units), referred to as "Funds" within WeGive. While the default mapping links WeGive's "Funds" to Salesforce's npsp__General_Accounting_Unit__c object, there's a customization option that allows users to define a different API name for "Funds" in Salesforce. This demonstrates the existing flexibility even without a dedicated UI.
Custom Field Mapping:
WeGive offers a high degree of flexibility for mapping custom fields between the systems. The system allows users to map WeGive's custom fields to any custom field in Salesforce.
Default Mapping Rules:
The code snippets in the sources reveal a significant detail about WeGive's integration architecture: default mapping rules are defined within the code itself. These rules establish the initial mappings between WeGive objects and fields and their corresponding Salesforce counterparts. These default rules provide a solid starting point and cover common use cases for synchronization.
Overriding Default Mappings:
Users can override these default mappings or add new custom field mappings using WeGive's Mapping Rules interface. The flexibility of custom field mapping allows organizations to:
Challenges and Considerations:
Although WeGive offers significant flexibility for mapping custom objects and fields, some challenges need to be addressed:
Overall, the WeGive-Salesforce integration aims for flexibility in handling custom object and field mappings. The current limitations in the UI are acknowledged, and there are plans to introduce improvements that will further enhance the flexibility and user experience. The integration's ability to accommodate diverse data structures and adapt to custom fields makes it a powerful tool for organizations seeking to synchronize data between WeGive and Salesforce.
Understanding the Basics
Utilizing Debugging Tools
Common Issues and Troubleshooting Steps
Proactive Measures
By following these steps and making use of the debugging tools available, you can effectively troubleshoot the WeGive-Salesforce integration, ensure data accuracy, and maintain a smooth flow of information between the two systems.
Regular maintenance and thoughtful software updates are essential for ensuring the smooth operation and long-term success of the WeGive-Salesforce integration. Here are suggestions based on the provided sources and our conversation:
By following these suggestions for regular maintenance and software updates, you can proactively address potential issues, minimize disruptions, and ensure the WeGive-Salesforce integration continues to meet your organization's needs reliably.
Organization Structure
The WeGive Salesforce integration allows for bi-directional data syncing, enabling organizations to leverage data from multiple sources for a unified digital experience.
The manual is designed for Salesforce administrators who need to understand, configure, and troubleshoot the integration, as well as admin users of a WeGive account.
You need a Salesforce account with administrator privileges and a WeGive account with Salesforce integration enabled.
The integration syncs data every 15 minutes to pull data from Salesforce, while pushes from WeGive to Salesforce happen with a 5-minute delay.
Yes, it is necessary to enable the OAuth username-password flow for Salesforce instances created after Summer 2023.
Yes, you can customize the mapping rules to fit your organization's needs.
You should review the integration logs in WeGive to identify the errors and troubleshoot accordingly.
Yes, there are default mapping rules that establish initial mappings between WeGive objects and their corresponding Salesforce counterparts.
You can contact support at [email protected].
This document explains the WeGive Salesforce integration, covering setup, configuration, debugging, and the data synchronization process.
WeGive pulls in data from various sources, including in-person payments, checks, stock donations, and more, ensuring a comprehensive view of donor activity. This positions WeGive as a Customer Data Platform (CDP).
It's designed for Salesforce administrators who need to understand, configure, and troubleshoot the integration who are also admin users of a WeGive account.
To get started with the WeGive Salesforce integration, you will need:
The integration relies on the OAuth username-password flow. This flow requires that you provide WeGive with the Salesforce connected app's client ID and client secret, and a Salesforce system administrator username and password. This allows WeGive to securely access and interact with your Salesforce data.
For Salesforce instances created after Summer 2023, the OAuth username-password flow must be explicitly enabled. Failure to do so will prevent the integration from connecting.
The connection will only be successful if both the WeGive and Salesforce instances are the same type (production or sandbox). You cannot connect a production WeGive account to a sandbox Salesforce instance, or vice versa.
The setup process assumes you have already enabled the Salesforce integration within your WeGive account, granting you access to the configuration settings.
Once the integration is enabled in WeGive, follow these steps to set it up in Salesforce:
1. Create a Connected App in Salesforce:
2. Access and Copy the Consumer Key and Secret Key:
3. Configure IP Relaxation Settings:
4. Add WeGive API as a Remote Site:
5. Enable Username-Password Flow for Instances Created After Summer 2023:
6. Configure Field-Level Security in Salesforce:
7. Input Salesforce Details in WeGive:
The WeGive Salesforce integration syncs every 15 minutes to pull data from Salesforce. Pushes from WeGive to Salesforce happen with a 5-minute delay for optimization. You can also manually trigger a sync from the integration settings page in WeGive.
Remember to refer to the help article provided by WeGive for detailed guidance throughout the setup process.
Key Points to Remember:
Here are some key elements and functionalities you can expect to find on this screen:
The exact appearance and functionalities of the WeGive Salesforce integration screen may vary depending on the specific version of WeGive you are using.
Setting up object and field mapping in the WeGive Salesforce integration involves configuring how data from specific objects and fields in WeGive corresponds to objects and fields in Salesforce. This mapping ensures that information is transferred accurately and consistently between the two platforms.
In WeGive, the mapping is primarily managed through the “Mapping Rules” section of the Salesforce integration settings. This section provides a visual interface to define the relationships between WeGive objects and fields and their counterparts in Salesforce. You can add new mappings, modify existing ones, or disable mappings that you don't need.
Mapping Rules Customization Options in WeGive:
Understanding Object Relationships:
You need to understand the default object relationships between WeGive and Salesforce. For example:
The integration syncs based on payments made in Salesforce. It will not function unless payments are being utilized within Salesforce.
Field-Level Security in Salesforce:
While WeGive handles the mapping rules, you need to ensure proper field-level security is configured within Salesforce. Even if your integration user is a system administrator, hidden fields in Salesforce will cause sync errors. To adjust field-level permissions:
Custom Objects in Salesforce:
Key Considerations:
By carefully configuring the object and field mapping in WeGive and Salesforce, and paying attention to field-level security settings in Salesforce, you can ensure smooth and accurate data synchronization between the two platforms, enabling a seamless flow of information between your fundraising and donor management systems.
Here are the default object mappings between WeGive and Salesforce:
WeGive
Salesforce
Donor (Individual)
Contact
Donor (Company)
Account
Household
Account (with Record Type = "Household Account")
Campaign
Campaign
Donation
Opportunity
Payment
Payment (npe01__OppPayment__c)
Recurring Plan
Recurring Donation (npe03__Recurring_Donation__c)
Designation
GAU (General Accounting Unit)
Pledge
Pledge_Plan__c (custom object)
Payout
Custom Object (details not specified)
Key Points about the Object Mappings:
It's crucial to understand that these are the default mappings. WeGive offers extensive customization options through Mapping Rules, allowing organizations to change how fields are mapped or disable the mapping entirely.
In addition to the direct object mappings, the integration considers related objects to ensure data consistency and maintain relationships. For instance, when syncing a Donation, the integration will take into account associated data like the Donor, Campaign, Recurring Plan, and Pledge, updating corresponding fields in Salesforce accordingly. This allows for a more comprehensive and accurate representation of giving data across both platforms.
The WeGive-Salesforce integration creates a bidirectional link between Contacts in Salesforce and individual donors in WeGive. If a donor doesn’t exist in Salesforce, the integration will create a new Contact and Account for that donor. When a donor already exists in Salesforce, the integration syncs the existing data with WeGive.
WeGive prioritizes syncing on emails. If a Salesforce instance has Contacts without emails, they may not be synced. By default, the integration is configured to only sync Contacts with emails, ensuring that the primary means of communication is consistently maintained. However, you can customize this setting in WeGive to sync all Contacts, regardless of whether they have an email address.
WeGive pulls data from Salesforce every 15 minutes, including updates to Contacts. Pushes to Salesforce from WeGive occur on a 5-minute delay.
Here is a list of fields that are mapped by default between WeGive and Salesforce for individual donors. These mappings can be customized in the WeGive platform:
WeGive Field → Salesforce Field
Note:
In addition to these fields, WeGive syncs other related data, such as the donor’s household, donation history, and recurring donation information.
When importing recurring donations from Salesforce, the relationship between the recurring donation and the donor can be controlled by how the data is set up in Salesforce. To attribute a recurring donation to a Company (Account) in WeGive, ensure the record in Salesforce only has an Account ID associated with it. If it has both a Contact ID and an Account ID, the recurring donation will be related to the primary Contact instead.
To ensure a successful and efficient sync:
In the WeGive-Salesforce integration, Salesforce Accounts represent two types of supporters in WeGive: Companies and Households.
It's important to understand how this object relationship interacts with the integration between individual donors in WeGive and Contacts in Salesforce:
Default Field Mappings for Accounts:
The following fields are mapped by default between WeGive and Salesforce for Companies and Households. You can customize these mappings in WeGive:
WeGive Field → Salesforce Field
Key Considerations:
By understanding the object relationships and field mappings for Accounts, you can ensure the integration effectively syncs Company and Household data between WeGive and Salesforce. Regularly reviewing the integration logs helps identify and address any inconsistencies or errors, ensuring data integrity and a comprehensive view of your supporters.
The WeGive-Salesforce integration establishes a bidirectional link between Campaigns in Salesforce and Campaigns in WeGive. This synchronization allows for the seamless flow of campaign data between the two platforms, ensuring consistency and facilitating comprehensive reporting and analysis.
Default Field Mappings:
The following fields are mapped by default between WeGive and Salesforce for campaigns. You can customize these mappings within the WeGive platform:
Note:
Use Cases:
Key Considerations:
By effectively leveraging the campaign integration, organizations can streamline their fundraising efforts, enhance reporting capabilities, and gain a more comprehensive understanding of their campaigns' impact.
The WeGive-Salesforce integration connects General Accounting Units (GAUs) in Salesforce with Designations in WeGive. This bi-directional synchronization ensures consistent data flow between the systems, streamlining fund management and reporting.
How This Integration is Used:
Additional Insights:
To gain a deeper understanding of the specific fields mapped for GAUs and Designations, you would need to consult the WeGive API documentation or reach out to WeGive support for a detailed list of available mappings. Regularly monitoring the integration logs in WeGive will also help identify and address any inconsistencies or errors during the synchronization process, ensuring data integrity.
The WeGive-Salesforce integration centers around payments, using Opportunities and Payments in Salesforce to represent Transactions in WeGive. It's important to note that WeGive syncs on the Payment level, not the Opportunity level. So, a single Opportunity in Salesforce with multiple Payments will be reflected as multiple, individual Transactions in WeGive.
Here's a breakdown of the key objects and field mappings:
1. Salesforce Opportunities:
2. Salesforce Payments (npe01__OppPayment__c):
Default Field Mappings for Transactions and Payments:
The sources don't provide a comprehensive list of all the default mappings. However, based on the available code snippets and context, here are some of the key fields that are likely mapped:
Associated Objects and Fields:
In addition to the fields listed above, the integration considers data from various associated objects to provide context and maintain relationships:
Important Considerations:
By understanding the relationships between Opportunities, Payments, and Transactions, as well as the default field mappings, you can ensure a smooth and accurate flow of payment data between WeGive and Salesforce. As always, diligently reviewing the integration logs in WeGive will help you identify and address any inconsistencies, ensuring your payment data is reliable and reflects your organization's financial activity.
The WeGive-Salesforce integration links Recurring Donations in Salesforce with Recurring Plans in WeGive, ensuring that recurring giving information is synchronized across both platforms. This synchronization facilitates a unified view of recurring donor activity and streamlines management.
While a complete list of default field mappings is not explicitly provided in the sources, the code excerpts and explanations offer insights into key fields and relationships that are considered.
Key Points to Understand:
Default Field Mappings (based on code and context):
Associated Objects and Considerations:
Using the Recurring Gift Integration Effectively:
The integration between recurring gifts in Salesforce and recurring plans in WeGive provides several benefits:
For a complete and up-to-date list of all default field mappings, you should consult the WeGive API documentation. In addition, regularly monitoring integration logs in WeGive can help identify and address any discrepancies that might arise, ensuring the accuracy and reliability of your recurring giving data.
The WeGive-Salesforce integration handles Pledges by utilizing a custom object in Salesforce named Pledge_Plan__c. This custom object is necessary because Salesforce does not have a native object specifically for pledges. The integration allows for the synchronization of pledge data between the two systems, ensuring that pledge information is consistently updated.
Here's a breakdown of the key aspects of the Pledge integration:
Default Field Mappings (based on the code and context):
Here are some of the fields that are likely mapped by default between WeGive's Pledge object and Salesforce's Pledge_Plan__c custom object:
WeGive Pledge Field
Salesforce Pledge_Plan__c Field
amount
Amount__c
donor.salesforce_id
Contact__c
donor.salesforce_account_id
Account__c
campaign.salesforce_id
Campaign__c
start_date
Date_Established__c
end_date
End_Date__c
fund.salesforce_id
GAU_Allocation__c
installment_frequency
Installment_Period__c
Associated Objects and Considerations:
The integration also considers various associated objects and fields to provide a complete picture of the pledge and its relationships:
While this information provides a good overview of the Pledge integration, it's important to note that a complete and up-to-date list of all default field mappings should be obtained from the WeGive API documentation. Regularly reviewing the WeGive integration logs is also highly recommended to identify and resolve any potential data discrepancies. This ensures that your pledge data is accurate and reflects the current status of pledges made through your organization.
Request information from your WeGive account manager.
Request information from your WeGive account manager.
Request information from your WeGive account manager.
Request information from your WeGive account manager.
Custom Object Mapping Process:
Currently, there is no dedicated user interface in WeGive for mapping custom objects, but WeGive is actively developing such a UI to streamline the process. Custom objects are mapped via request. Custom fields are mapped via the UI.
Steps:
Flexibility of Custom Object Mapping:
Charlie emphasizes that WeGive doesn't require a strict adherence to specific object structures in Salesforce. The system is designed to be flexible, as long as the custom object in Salesforce:
Example (GAU/Funds):
Charlie highlights an existing example of custom object mapping with GAUs (General Accounting Units), referred to as "Funds" within WeGive. While the default mapping links WeGive's "Funds" to Salesforce's npsp__General_Accounting_Unit__c object, there's a customization option that allows users to define a different API name for "Funds" in Salesforce. This demonstrates the existing flexibility even without a dedicated UI.
Custom Field Mapping:
WeGive offers a high degree of flexibility for mapping custom fields between the systems. The system allows users to map WeGive's custom fields to any custom field in Salesforce.
Default Mapping Rules:
The code snippets in the sources reveal a significant detail about WeGive's integration architecture: default mapping rules are defined within the code itself. These rules establish the initial mappings between WeGive objects and fields and their corresponding Salesforce counterparts. These default rules provide a solid starting point and cover common use cases for synchronization.
Overriding Default Mappings:
Users can override these default mappings or add new custom field mappings using WeGive's Mapping Rules interface. The flexibility of custom field mapping allows organizations to:
Challenges and Considerations:
Although WeGive offers significant flexibility for mapping custom objects and fields, some challenges need to be addressed:
Overall, the WeGive-Salesforce integration aims for flexibility in handling custom object and field mappings. The current limitations in the UI are acknowledged, and there are plans to introduce improvements that will further enhance the flexibility and user experience. The integration's ability to accommodate diverse data structures and adapt to custom fields makes it a powerful tool for organizations seeking to synchronize data between WeGive and Salesforce.
Understanding the Basics
Utilizing Debugging Tools
Common Issues and Troubleshooting Steps
Proactive Measures
By following these steps and making use of the debugging tools available, you can effectively troubleshoot the WeGive-Salesforce integration, ensure data accuracy, and maintain a smooth flow of information between the two systems.
Regular maintenance and thoughtful software updates are essential for ensuring the smooth operation and long-term success of the WeGive-Salesforce integration. Here are suggestions based on the provided sources and our conversation:
By following these suggestions for regular maintenance and software updates, you can proactively address potential issues, minimize disruptions, and ensure the WeGive-Salesforce integration continues to meet your organization's needs reliably.
Organization Structure
The WeGive Salesforce integration allows for bi-directional data syncing, enabling organizations to leverage data from multiple sources for a unified digital experience.
The manual is designed for Salesforce administrators who need to understand, configure, and troubleshoot the integration, as well as admin users of a WeGive account.
You need a Salesforce account with administrator privileges and a WeGive account with Salesforce integration enabled.
The integration syncs data every 15 minutes to pull data from Salesforce, while pushes from WeGive to Salesforce happen with a 5-minute delay.
Yes, it is necessary to enable the OAuth username-password flow for Salesforce instances created after Summer 2023.
Yes, you can customize the mapping rules to fit your organization's needs.
You should review the integration logs in WeGive to identify the errors and troubleshoot accordingly.
Yes, there are default mapping rules that establish initial mappings between WeGive objects and their corresponding Salesforce counterparts.
You can contact support at [email protected].