Known Limitations & Workarounds

This article documents current limitations of the NPC integration and available workarounds. We'll update this as limitations are resolved in future releases.

Login Contact Roles Not Supported on NPC

Status: Known issue (WEG-6631)

What's happening: The Login Contact Roles feature in WeGive is not functional on NPC orgs. The feature currently queries AccountContactRole, which is a legacy Salesforce object. NPC uses AccountContactRelation instead.

Impact: If you enable Login Contact Roles in your NPC integration settings, no portal logins will be created.

Workaround: Do not enable Login Contact Roles until this is resolved. If you need to manage contact-to-account relationships for portal access, create them directly in Salesforce using AccountContactRelation.

Push/Pull Toggle Naming Inconsistency

Status: Known issue (WEG-6632)

What's happening: On the push side, there's a single "Push Supporters" toggle that covers both individual (Person Account) and organization supporters. On the pull side, these are split into separate toggles: "Pull Supporters" (Person Accounts only) and "Pull Companies" (Organization Accounts only).

Impact: This can be confusing during initial setup. The functionality works correctly — the naming is just inconsistent.

Workaround: When configuring pull settings, enable both "Pull Supporters" and "Pull Companies" if you want to pull all supporter types. This is equivalent to what the single "Push Supporters" toggle does on the push side.

Sync Modal Dropdown Not Scrollable

Status: Known issue (WEG-6633)

What's happening: In the manual Sync NPC modal, the Data Set dropdown list cuts off after a certain number of options and cannot be scrolled to show additional data types.

Impact: You may not be able to select specific data types for a targeted manual sync.

Workaround: Select "All entities" to sync everything. This achieves the same result but syncs all data types rather than a specific one.

GiftType Is a Restricted System Picklist

What's happening: The GiftType field on GiftTransaction is a restricted system picklist controlled by Salesforce. You cannot add, remove, or rename the values (Major Gift, Recurring Gift, Standard Gift).

Impact: If you expected to customize GiftType values to match your organization's categorization, that's not possible. WeGive's "Pull Gift Types" setting pulls these fixed values for use as filters — it does not allow configuration.

Workaround: If you need custom gift categorization, create a custom picklist field on GiftTransaction and use a custom field mapping in WeGive to populate it.

Person Accounts Are Required and Irreversible

What's happening: NPC uses Person Accounts for individual supporters. Enabling Person Accounts in Salesforce is a permanent, irreversible change to your org.

Impact: Once Person Accounts are enabled, they cannot be disabled. This affects how Contacts and Accounts work throughout your entire Salesforce org, not just for the WeGive integration.

Workaround: There is no workaround — Person Accounts are a core NPC requirement. Make sure you understand the implications before enabling them. Work with your Salesforce consultant to plan the transition, especially if you have existing Contacts that need to be converted.

Fee Details Not Synced in v1

What's happening: Processing fee details (fee amount, net amount, cover fee flag) are not included in the initial NPC integration release. These WeGive fields don't have native NPC equivalents.

Impact: Fee data won't appear on GiftTransaction records unless you set up custom field mappings.

Workaround: Create custom Currency fields on GiftTransaction in Salesforce (e.g., Fee_Amount__c, Net_Amount__c) and map them using WeGive's custom field mapping settings. Note that if WeGive ships a managed package with these fields later, you may end up with duplicates.

Source Attribution Not Synced in v1

What's happening: UTM tracking, checkout references, and form source data are not included in the default field mappings.

Workaround: Same approach as fee details — create custom fields in Salesforce and use custom field mappings. Common fields to create:

• UTM_Source__c (Text)

• UTM_Medium__c (Text)

• UTM_Campaign__c (Text)

• Checkout_Reference__c (Text)

API Call Volume on High-Volume Orgs

What's happening: The integration makes API calls to Salesforce during each sync cycle across multiple object types. For most orgs this is well within Salesforce's API limits, but very high-volume orgs or orgs with limited API allocations may need to monitor usage.

Workaround: Monitor your Salesforce API usage in Setup → System Overview. If you're concerned about limits, contact your WeGive CS representative to discuss your org's expected sync volume and explore options like reducing pull frequency or limiting which object types sync.