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

    Heads up — I ran into this exact thing last month. The workaround Eli mentioned works, but YMMV depending on how your org handles record visibility.

    In my case, the fields were on Opportunities owned by users in a different Role hierarchy that the integration user couldn't see via sharing rules, even with "View All" on the object. The SOQL worked in Dev Console because I was running as myself, not as the integration user.

    Worth doing an EXECUTE AS check:

    System.runAs(integrationUser) {
    List<Opportunity> recent = [SELECT Custom_Field__c FROM Opportunity LIMIT 1];
}

    If that throws no rows or null values, the visibility issue is at the record level, not field level.

    Also — the upcoming update Eli mentioned is tracked in API v2.1 Now Available with Webhook Improvements (scroll to "Salesforce Metadata Handling"), though it doesn't mention the sampling removal yet.

Reply
  • 0

    Heads up — I ran into this exact thing last month. The workaround Eli mentioned works, but YMMV depending on how your org handles record visibility.

    In my case, the fields were on Opportunities owned by users in a different Role hierarchy that the integration user couldn't see via sharing rules, even with "View All" on the object. The SOQL worked in Dev Console because I was running as myself, not as the integration user.

    Worth doing an EXECUTE AS check:

    System.runAs(integrationUser) {
    List<Opportunity> recent = [SELECT Custom_Field__c FROM Opportunity LIMIT 1];
}

    If that throws no rows or null values, the visibility issue is at the record level, not field level.

    Also — the upcoming update Eli mentioned is tracked in API v2.1 Now Available with Webhook Improvements (scroll to "Salesforce Metadata Handling"), though it doesn't mention the sampling removal yet.

Children
No Data