When fields are ingested from the local Salesforce environment via Data Sync in CRM Analytics, certain parameters are controlled by the ingestion metadata, or schema, of the object's Data Sync definition. This metadata cannot be edited from the "Preview Source Data" field configuration in Data Sync's object configuration.
Note: Field metadata for Remote Data Connectors generally can be edited in the field attributes pane of the "Preview Source Data" configuration screen. This article applies to the Salesforce Local Sync (also known as SFDC_Local or Replication).
Ingestion metadata (which includes all the parameters documented in Overriding Salesforce Field Metadata, e.g.: fiscalMonthOffset) must be specified in the sfdcDigest node of a dataflow. Data Sync metadata combines all the different sfdcDigest nodes on the same object from all dataflows and uses the value for each parameter from the most recently updated dataflow definition where it exists. This is noted in Understand What Happens When You Enable Data Sync and Connections.
If a field's metadata is invalid (for example, the Precision on a text field exceeds 32,000) then the field will have a warning icon in the Data Sync object configuration and the Save button will be non-interactive. All fields with invalid metadata will need to be corrected by the process covered below prior to saving any changes to the object's data sync configuration.
While parameters like "fiscalMonthOffset" and "firstDayOfWeek" are present in the Extended Metadata (XMD) file associated with a dataset, they are deprecated and have no impact on the dataset fields or behavior. To ensure that the date fields have fiscal date parts generated, they must have a "fiscalMonthOffset" defined in the ingestion metadata. Note the "Fiscal Periods in CRM Analytics" section in Date Formats and Fiscal Dates for Source Data. As a best practice, we recommend setting the "fiscalMonthOffset" and "firstDayOfWeek" to the same value for all dates in a source object.
To update ingestion metadata, create a dedicated 'master' dataflow that sets the correct metadata values. This dataflow does not need to be run — simply saving it updates the Data Sync metadata.
This will set the defined parameters for all the included objects and fields in Data Sync and allow consistent behaviour in Data Prep Recipes, dataflows, and datasets.
Please be aware that any metadata overrides in any other dataflows will overwrite the Data Sync metadata if that dataflow is updated after performing the above actions. To avoid this, either have consistent metadata overrides in all dataflows or remove metadata overrides from all dataflows other than the "master" dataflow created in the steps above.
000392328

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.