• 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

    Thank you both. I have identified the root cause.

    Following Devon's suggestion, I executed a query as the integration user and confirmed that the custom fields are indeed visible. However, I then examined the Opportunity records more closely and determined that the custom fields were created recently and the existing Opportunities had not yet been backfilled with data.

    After populating a test Opportunity record with values in all custom fields and clicking "Refresh Fields" in FieldPulse, the fields now appear correctly in the mapping interface.

    From a governance perspective, it is worth noting that this behavior creates a dependency on data presence that may not be intuitive for administrators configuring the integration. I would recommend updating the documentation to clarify this requirement, or preferably, removing the sampling limitation as indicated in the upcoming release.

    I will proceed with field mapping configuration. Thank you for the assistance.

Reply
  • 0

    Thank you both. I have identified the root cause.

    Following Devon's suggestion, I executed a query as the integration user and confirmed that the custom fields are indeed visible. However, I then examined the Opportunity records more closely and determined that the custom fields were created recently and the existing Opportunities had not yet been backfilled with data.

    After populating a test Opportunity record with values in all custom fields and clicking "Refresh Fields" in FieldPulse, the fields now appear correctly in the mapping interface.

    From a governance perspective, it is worth noting that this behavior creates a dependency on data presence that may not be intuitive for administrators configuring the integration. I would recommend updating the documentation to clarify this requirement, or preferably, removing the sampling limitation as indicated in the upcoming release.

    I will proceed with field mapping configuration. Thank you for the assistance.

Children
No Data