• State Verified Answer
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 2 subscribers
  • Views 2 views
  • Users 0 members are here
Options
Related

Salesforce custom fields not appearing in mapping screen

Anita Sharma

I have completed the initial configuration of the Salesforce integration per the documentation. The connection is established and standard objects (Account, Contact, Opportunity) are visible in the FieldPulse mapping interface. However, I have confirmed that custom fields created in Salesforce are not appearing as available fields for mapping.

Specifically, I have verified the following:

  1. The custom fields are created on the Opportunity object in Salesforce.
  2. The API names are properly formatted (using __c suffix as expected).
  3. The FieldPulse integration user has read access to these fields via the assigned Profile and Permission Sets.
  4. The fields are populated with data in at least one existing Opportunity record.
  5. I have attempted to refresh the field list in the FieldPulse mapping screen using the "Refresh Fields" button located at the bottom of the mapping table.

The Salesforce organization is running API version 59.0. FieldPulse account is on the Enterprise tier.

Is there a known limitation regarding which field types are exposed, or is there a synchronization delay I should account for? I have waited approximately 45 minutes since field creation in case caching is involved.

Reference: Configuration performed per Connecting FieldPulse to Salesforce.

Parents
  • 0

    Hey Anita — Leo's absolutely right about field-level security being the usual culprit, but since you've confirmed that's set up properly, let me dig into what's happening here.

    The mapping screen pulls from a cached metadata snapshot that's refreshed when you hit "Refresh Fields," but there's a quirk: we only surface custom fields that have at least one record with a non-null value in your Salesforce org. This is an optimization to keep the mapping UI from being overwhelmed with unused legacy fields, but I realize it's not documented as clearly as it should be.

    Can you confirm:

    1. Do these custom fields have values in Opportunity records that were created or updated after the integration was initially connected? We sample a window of recent records.
    2. Are any of the fields on Opportunities that are owned by the integration user itself, or only on records owned by others?

    If the fields are populated but still not appearing, I can trigger a manual metadata refresh on our side. Also worth noting: we're rolling out an update in the next two weeks that removes this sampling restriction entirely — all readable fields will appear regardless of data presence.

    In the meantime, if you need an immediate workaround, creating a test Opportunity with values in all the custom fields and then clicking "Refresh Fields" again should surface them.

    Let me know what you find and I can escalate if needed.

Reply
  • 0

    Hey Anita — Leo's absolutely right about field-level security being the usual culprit, but since you've confirmed that's set up properly, let me dig into what's happening here.

    The mapping screen pulls from a cached metadata snapshot that's refreshed when you hit "Refresh Fields," but there's a quirk: we only surface custom fields that have at least one record with a non-null value in your Salesforce org. This is an optimization to keep the mapping UI from being overwhelmed with unused legacy fields, but I realize it's not documented as clearly as it should be.

    Can you confirm:

    1. Do these custom fields have values in Opportunity records that were created or updated after the integration was initially connected? We sample a window of recent records.
    2. Are any of the fields on Opportunities that are owned by the integration user itself, or only on records owned by others?

    If the fields are populated but still not appearing, I can trigger a manual metadata refresh on our side. Also worth noting: we're rolling out an update in the next two weeks that removes this sampling restriction entirely — all readable fields will appear regardless of data presence.

    In the meantime, if you need an immediate workaround, creating a test Opportunity with values in all the custom fields and then clicking "Refresh Fields" again should surface them.

    Let me know what you find and I can escalate if needed.

Children
No Data