• State Verified Answer
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 2 subscribers
  • Views 0 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

    Glad we got you unblocked, Anita — and thank you for the detailed follow-up. You're absolutely right that this behavior is under-documented; I'm flagging this with our docs team to get the "data presence" requirement added to Connecting FieldPulse to Salesforce this week.

    I've also linked your feedback to the internal ticket for the sampling removal (FP-7821) as additional confirmation that we should prioritize the broader field visibility change.

    I'll circle back here once that ships. If you hit any other issues with the mapping itself, feel free to @ me directly.

Reply
  • 0

    Glad we got you unblocked, Anita — and thank you for the detailed follow-up. You're absolutely right that this behavior is under-documented; I'm flagging this with our docs team to get the "data presence" requirement added to Connecting FieldPulse to Salesforce this week.

    I've also linked your feedback to the internal ticket for the sampling removal (FP-7821) as additional confirmation that we should prioritize the broader field visibility change.

    I'll circle back here once that ships. If you hit any other issues with the mapping itself, feel free to @ me directly.

Children
No Data