Loading

Splitweek Measures Export Behavior and Configuration Restrictions

Publiseringsdato: Jun 8, 2026
Beskrivelse

Export jobs that include KPIs with splitweek time dimensions are subject to specific configuration requirements. Two aspects govern the data fetching and splitweek behavior:

Aspect 1: Data Fetching Behavior (Writeback Setting)

  • When writeback = true:
    • Data is read directly from offcore.
    • Export works as expected.
  • When writeback = false:
    • Data does not come from offcore; instead, it is calculated on the go.
    • For the export to succeed, all of the following conditions must be met:
      • All dependent KPIs must have the Writeback setting enabled (true).
      • All dependent KPIs must be included in the export configuration.
      • If these conditions are not met, the calculated KPI will not be computed correctly and the export may fail or crash.

Aspect 2: Splitweek Data Availability

  • A KPI has splitweek data if:
    • timedimension.splitweeks = true at the top-level meta configuration, AND
    • All dependent KPIs are splitweek-enabled.
  • A KPI does NOT have splitweek data if:
    • timedimension.splitweeks = false at the top-level meta configuration, OR
    • Any dependent KPI is splitweek-disabled.

 

Configuration Matrix

The table below summarizes the possible configuration combinations and their expected export outcomes. Refer to the full Splitweek Config Matrix for detailed scenarios including both success and failure cases.

KPI ConfigurationDependent KPI ConfigurationTime Dimension in Export ConfigurationResult
"storageoptions.writeback": true
"storageoptions.subperiod": "weeksplits"		N/Atimedimension.splitweeks = true✅ Exports a report with split week KPI data
"storageoptions.writeback": true
"storageoptions.subperiod": "none"		N/Atimedimension.splitweeks = true❌ Export produces empty cells for this KPI and may crash the export job.
"storageoptions.writeback": falseAll dependent KPIs:
"storageoptions.writeback": true
"storageoptions.subperiod": "weeksplits"

All dependent KPIs included in export meta

If one or more dependent KPI has:
"storageoptions.writeback": false OR If anyone is missing may lead to empty cell in final export for the given KPI		timedimension.splitweeks = true✅ Exports a report with split week KPI data calculated on-the-fly
"storageoptions.writeback": falseAll dependent KPIs:
"storageoptions.writeback": true
"storageoptions.subperiod": "none"

All dependent KPIs included in export meta

If one or more dependent KPI has:
"storageoptions.writeback": false OR If anyone is missing may lead to empty cell in final export for the given KPI		timedimension.splitweeks = true❌ Export produces empty cells for this KPI and may crash the export job.
"storageoptions.writeback": true
"storageoptions.subperiod": "weeksplits"		N/Atimedimension.splitweeks = false✅ Exports a report without split week KPI data
"storageoptions.writeback": true
"storageoptions.subperiod": "none"		N/Atimedimension.splitweeks = false✅ Exports a report without split week KPI data
"storageoptions.writeback": falseAll dependent KPIs:
"storageoptions.writeback": true
"storageoptions.subperiod": "none"

All dependent KPIs included in export meta

If one or more dependent KPI has:
"storageoptions.writeback": false OR If anyone is missing may lead to empty cell in final export for the given KPI		timedimension.splitweeks = false✅ Exports a report with standard week KPI data calculated on-the-fly
"storageoptions.writeback": falseAll dependent KPIs:
"storageoptions.writeback": true
"storageoptions.subperiod": "weeksplits"

All dependent KPIs included in export meta

If one or more dependent KPI has:
"storageoptions.writeback": false OR If anyone is missing may lead to empty cell in final export for the given KPI		timedimension.splitweeks = false✅ Exports a report without split week KPI data

 

Løsning

To ensure a successful splitweek data export, follow these best practices:

  1. Enable Writeback on the primary KPI (writeback = true) wherever possible. This is the recommended and most reliable configuration for export jobs.
  2. If Writeback must be false, ensure the following:
    1. All dependent KPIs have writeback = true.
    2. All dependent KPIs are explicitly included in the export configuration. Omitting even one dependent KPI will cause the export to fail or crash.
  3. Verify the timedimension.splitweeks setting at the top-level meta configuration:
    1. Set to true if splitweek data is required for the KPI.
    2. Ensure that all dependent KPIs are also splitweek-enabled. If any dependent KPI has splitweek disabled, the parent KPI will not have splitweek data.
  4. Review the Splitweek Config Matrix  before configuring export jobs to identify the expected behavior for your specific configuration combination.
  5. Refer to the Consumer Goods Developer Guide for additional context on timedimension configuration: https://developer.salesforce.com/docs/atlas.en-us.retail_api.meta/retail_api/rtr_configuration_integration_meta.htm
Knowledge-artikkelnummer

005385612

 
Laster
Salesforce Help | Article