--- schema_version: "1" id: 5bb3f4f039209b9c26559ac2be33bf806e89b664e4362c4f33d2be9cb942f13c title: Overriding Salesforce Field Metadata collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/analytics/264-0-0/bi_integrate_salesforce_extract_transformation_override_metadata.md canonical_url: https://help.salesforce.com/s/articleView?id=analytics.bi_integrate_salesforce_extract_transformation_override_metadata.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 8fbd0700f8ead0e06f823107c86f7a840d191832ff00c81a8d12606a53159e28 description: You can override the field metadata that the sfdcDigest transformation extracts from a Salesforce object to make the data appear differently in a dataset. For example, CRM Analytics can add a default value to records that have missing values for a field. products: - CRM Analytics - Cross Cloud release: "264" --- # Overriding Salesforce Field Metadata You can override the field metadata that the sfdcDigest transformation extracts from a Salesforce object to make the data appear differently in a dataset. For example, CRM Analytics can add a default value to records that have missing values for a field. You can add these field parameters to the sfdcDigest transformation node to override the field metadata: - defaultValue - type - fiscalMonthOffset - isYearEndFiscalYear - firstDayOfWeek - isMultiValue - multiValueSeparator (not available in dataflow editor) - precision - scale For a description of each of these field parameters, see [Field Parameters](https://help.salesforce.com/s/articleView?id=analytics.bi_integrate_salesforce_extract_transformation_operation.htm&release=264.0.0&type=5 "When you define an sfdcDigest transformation, you set the action attribute to sfdcDigest and specify the parameters for the object and fields that you want to extract. Optionally, you can also specify parameters to filter the records extracted from the Salesforce object."). ## Custom Field Considerations Your source data can include custom fields with different API names that share label values. To avoid confusion when viewing the fields in the UI, you can: - Ingest the fields with different label names. - Use the [computeExpression](https://help.salesforce.com/s/articleView?id=analytics.bi_integrate_saql_transformation.htm&release=264.0.0&type=5 "The computeExpression transformation enables you to add derived fields to a dataset. The values for derived fields aren’t extracted from the input data source. Instead, CRM Analytics generates the values using a SAQL expression, which can be based on one or more fields from the input data or other derived fields. For example, you can use an expression to assign a value to a field, concatenate text fields, or perform mathematical calculations on numeric fields.") transformation to change the label values. - Use dataset-level [Analytics Extended Metadata (XMD)](https://developer.salesforce.com/docs/analytics/bi-dev-guide-xmd/guide/bi-xmd-edit.html) to modify the label values. ![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/images/icon_example.png) Example For example, you want to override metadata extracted from the Opportunity object. To override field metadata from the Opportunity object, you add the bold text to the sfdcDigest node in the dataflow definition file. ``` { "Extract_Opportunities": { "action": "sfdcDigest", "parameters": { "object": "Opportunity", "fields": [ { "name": "Id" }, { "name": "Name" }, { "name": "Amount", "defaultValue":"0", "precision":18, "scale":2 }, { "name": "StageName" }, { "name": "CloseDate", "fiscalMonthOffset":9, "firstDayOfWeek":2, "isYearEndFiscalYear":true }, { "name":"AccountId" }, { "name":"OwnerId" }, { "name": "OpportunitySupportTeamMembers__c", "type":"Text", "isMultiValue":true, "multiValueSeparator":",", "precision":255 } ] } }, "Register_Opportunities_Dataset":{ "action":"sfdcRegister", "parameters":{ "alias":"Opportunities", "name":"Opportunities", "source":"Extract_Opportunities" } } } ``` If you’re working in the dataflow editor, click the sfdcDigest node and then click ![Pencil button that appears next to selected fields in the sfdcDigest node](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/bi/images/bi/bi_integrate_dataflow_editor_edit_field_attributes_button.png) next to the field that you want to change. ![sfdcDigest node in dataflow editor with the pencil icon highlighted next to a selected field](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/bi/images/bi/bi_integrate_dataflow_editor_sfdcdigest_node.png) Update the field attributes, and then click **Save**. ![Override field attributes dialog in dataflow editor](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/bi/images/bi/bi_integrate_dataflow_editor_override_field_attributes.png) ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/images/icon_note.png) Note Changing a field’s type attribute to anything other than Text can result in an error in your dataflow or unexpected values in your datasets. For example, if you change a text field to a numeric field, you see an error when you try to update the dataflow. #### See Also - [sfdcDigest Transformation](https://help.salesforce.com/s/articleView?id=analytics.bi_integrate_salesforce_extract_transformation.htm&release=264.0.0&type=5 "phThe sfdcDigest transformation generates a dataset based on data that it extracts from a Salesforce object. You specify the Salesforce object and fields from which to extract data. You can choose to exclude particular fields that contain sensitive information or that aren’t relevant for analysis.")