--- schema_version: "1" id: aa4c34cdc6a3eeaf08560fba5e30460c9c28182a80ee47838ad0f6cbf6696299 title: Considerations for Syncing Salesforce Spiff Fields for Data 360 Reporting collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/spiff_data_cloud_considerations.md canonical_url: https://help.salesforce.com/s/articleView?id=sales.spiff_data_cloud_considerations.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 9d6dee3d222ec4a461731dcabb2bf09defc55aaaaac99671785024ed7e3f4eb9 description: When you add Salesforce Spiff fields for Data 360 reporting, keep a few points in mind. products: - Sales Cloud - Sales Enablement release: "264" --- # Considerations for Syncing Salesforce Spiff Fields for Data 360 Reporting When you add Salesforce Spiff fields for Data 360 reporting, keep a few points in mind. ### Required Editions
Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience
Available in: Enterprise, Unlimited, and Developer Editions
Available for an additional cost in: Professional Edition with Web Services API Enabled
A field is available to configure as a reporting field only if it meets one of these conditions. - The field is added to a plan statement for display as a metric card (worksheet calculations) or as a table display field (datasheet calculations). - The field is calculated in the trace tree. Calculations used in payout logic are included in the trace. A field can exist in Designer logic but not be reportable because of one of these reasons. - Trace is turned off for that field or one of its parent fields. - It's a best practice to encapsulate connector fields in a calculation field. Connector fields (like `__c` fields from Salesforce) can be used in logic. But for best results, they should be wrapped in a calculation for reporting and for easy changes if a field needs to change. A field can exist but have a null value for a given record because of one of these reasons. - The field was added to the calculation logic or the trace after the statement had been frozen. - A parent node has been overwritten. Overwriting a field at the root of the calculation tree makes any of its child fields (subbranches) unavailable for reporting. That is to say, overwriting a field essentially prunes the tree such that any pruned branches or sub-branches are null. - Conditional logic routed the calculation down another branch in the tree. A field must be a branch followed in the calculation to be included in the trace (and to be available for reports). - For example, if an `if` statement follows the `true` path, any child fields of the `false` path will neither be calculated in the trace nor available as a reporting field. The converse is also true. - Logical operators negate the need for the field to be calculated. - For example, if the first condition in an `AND` clause is false, the second condition won't be calculated in the trace. Any child fields of the second condition will not be available as a reporting field. - If the first condition in an `OR` clause is true, the second condition won't be calculated in the trace. Any child fields of the second condition won't be available as a reporting field. - The field is a record or a list. Records and lists aren't available as a reporting field. #### See Also - [Connector Fields and Calculations in Salesforce Spiff Reports](https://help.salesforce.com/s/articleView?id=sales.spiff_report_fields.htm&release=264.0.0&type=5 "When you’re using connector fields or calculations in Salesforce Spiff reports, encapsulate each those items in their own calculated field.") - [Add a Designer Field or Calculation to a Report in Salesforce Spiff](https://help.salesforce.com/s/articleView?id=sales.spiff_report_fields_add.htm&release=264.0.0&type=5 "Reports in Salesforce Spiff are generated from fields and metrics used in plan statements or commission logic. Designer fields or calculations not used in statements or commission logic aren't available for reports by default. To show one of these fields in a report, add the field to the payout rule that calculates commission.") - [Capture Trace View in Salesforce Spiff](https://help.salesforce.com/s/articleView?id=sales.spiff_trace.htm&release=264.0.0&type=5 "Admins and reps in Salesforce Spiff can visualize how metrics, rule totals, and deal amounts are calculated in statements. In trace view, also called Capture Trace, users can click into a highlighted item and view more details. Tracing calculations in Spiff helps you debug calculations, test new calculations, provide transparency, or conduct an audit. Admins can turn off trace for some items in Designer.")