What type of fields are not supported by the Marketing Cloud Account Engagement sync?

What type of fields are not supported by the Marketing Cloud Account Engagement sync?
A . Record Type fields
B . Formula fields
C . Number fields
D . Geolocation fields
E . Text Area (rich) fields

View Answer

Answer: B, D, E

Explanation:

According to the Salesforce documentation, the types of fields that are not supported by the Marketing Cloud Account Engagement sync are: B) Formula fields, D) Geolocation fields, and E) Text Area (rich) fields. A Marketing Cloud Account Engagement sync is a feature that allows users to connect and exchange data between Marketing Cloud Account Engagement and Salesforce fields, such as name, email, score, or grade. A Marketing Cloud Account Engagement sync can be configured by the administrator in the connector settings, and it can be customized for different objects, fields, or actions. A Marketing Cloud Account Engagement sync can support different types of fields, such as text, number, date, checkbox, picklist, or lookup fields. However, a Marketing Cloud Account Engagement sync cannot support some types of fields, such as formula, geolocation, or text area (rich) fields. A formula field is a field that calculates a value based on a formula or an expression. A geolocation field is a field that stores the latitude and longitude coordinates of a location. A text area (rich) field is a field that allows users to enter formatted text, images, or links. These types of fields are not supported by the Marketing Cloud Account Engagement sync, as they are either incompatible, complex, or large for the data exchange. A record type field is a type of field that is supported by the Marketing Cloud Account Engagement sync, as it is a field that defines different business processes, page layouts, or picklist values for different users. A number field is also a type of field that is supported by the Marketing Cloud Account Engagement sync, as it is a field that stores numerical values.

Reference: Salesforce documentation