Loading

CRM Analytics: Custom fields not visible in Data Manager when adding fields to data sync

Publish Date: May 27, 2026
Description

In CRM Analytics, when you navigate to Analytics Studio > Data Manager > Connect, click a connected Salesforce object, and select Edit Object Fields, custom fields — including text-type fields, formula fields, and managed package fields (for example, fields prefixed with vlocity_cmt__) — are absent from the column list and cannot be selected for data sync.

When a recipe attempts to use a field that was not included in the sync, the recipe fails with: "All fields used in a recipe must be included in data sync. Add the field [FieldName__c] from object [Object] to data sync for your local Salesforce connection."

Root cause: Two confirmed causes exist:

  1. The Analytics Cloud Integration User and/or Analytics Cloud Security User profile does not have Read field-level security access on the missing field — even if the field is visible to standard users.
  2. The field is listed in the Sync Ignored Fields custom metadata type, which suppresses it from the Data Manager picker.

Affected configuration:

  • Licenses: CRM Analytics Growth, Plus, and CRM Analytics for Financial Services
  • Releases: Summer '24 and later
  • Affected objects: Any connected Salesforce object (for example, Account, Contact, AssessmentQuestionResponse)
Prerequisite(s)
  • CRM Analytics Growth, Plus, or CRM Analytics for Financial Services license
  • Summer '24 or later
  • Connected Salesforce data source configured in Data Manager
  • System Administrator access to Object Manager, User management, and Custom Metadata Types
  • Analytics Cloud Integration User and Analytics Cloud Security User present and Active in the org
Resolution

Work through each cause in order. Most cases are resolved by Cause 1.

Cause 1: Analytics integration profiles lack field-level security on the missing field

  1. From Setup, open Object Manager and open the object that owns the missing field (for example, Account or AssessmentQuestionResponse).
  2. Click Fields & Relationships, then click the missing field (for example, Salesoffice__c or ResponseValue).
  3. Click Set Field-Level Security.
  4. For the Analytics Cloud Integration User profile, select the Visible checkbox.
  5. For the Analytics Cloud Security User profile, select the Visible checkbox.
  6. Click Save.
  7. From Setup, navigate to Users and confirm the Analytics Cloud Integration User and Analytics Cloud Security User are Active (not Frozen). If frozen, open the user record and click Unfreeze.
  8. Open Analytics Studio > Data Manager > Connect, click the connected object, and click Edit Object Fields. Search for the field, select its checkbox, and click Save.
  9. Click the dropdown next to the object name, select Run Data Sync, and choose Run Full Sync.

Cause 2: Field excluded by Sync Ignored Fields custom metadata type

  1. From Setup, search for Custom Metadata Types in Quick Find and click Custom Metadata Types.
  2. Next to Sync Ignored Fields, click Manage Records.
  3. Review the records. Each record specifies an Object API Name and a Field API Name that is suppressed from data sync.
  4. If the missing field appears in this list, click Del next to that record to remove the exclusion. If the record belongs to a managed package, clone the metadata to a new record with the field removed, following your change-control process.
  5. Return to Analytics Studio > Data Manager > Connect, open the object, and confirm the field now appears. Select it and click Save.

Cause 3: Managed package fields (for example, vlocity_cmt__ namespace)

  1. Repeat the field-level security steps in Cause 1 for the managed package field on both the Analytics Cloud Integration User and Analytics Cloud Security User profiles. Managed package fields require explicit FLS visibility on these profiles even when visible to standard users.
  2. Refresh your browser cache and reopen Data Manager > Connect > Edit Object Fields.

Confirm the fix: Open Analytics Studio > Data Manager > Connect, select the object, click Edit Object Fields, search for the field by API name, select it, save, and run a full data sync. The Jobs Monitor must report the sync job as Successful, and the field must be selectable in downstream recipe input nodes.

Knowledge Article Number

005385122

 
Loading
Salesforce Help | Article