Considerations for Syncing Salesforce Spiff Fields for Data 360 Reporting

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.