Mismatch in default time period selection
When default time period selections are not defined in dataflow annotations
And when the DE default time period selection config settings only mention the start period such as:
"period": {
"boundaries": ["1940", "2095"],
"default": ["2020", ""]
}
Then the DE displays a wrong end period selection in the time period filter:
Additional issue information
The data availability of the underlying dataflow has the following (correct) start and end periods:
<common:KeyValue id="TIME_PERIOD">
<common:TimeRange>
<common:StartPeriod isInclusive="true">1987-04-01T00:00:00</common:StartPeriod>
<common:EndPeriod isInclusive="true">2020-06-30T00:00:00</common:EndPeriod>
</common:TimeRange>
</common:KeyValue>
See:
ABS-CAPEX-1.1.0-structure.xml
ABS_CAPEX_1.1.0_eg-data.csv
This example dataflow ABS:CAPEX(1.1.0) was also loaded into qa:stable.
The issue disappears when the default end period selection config setting is defined.
The issue was observed in the ABS instance of Data Explorer, running the April 27 release.
Note that it is not possible to reproduce the issue in QA or Staging because the default time period selection config settings are complete in these environments.
Expected behaviour:
The start and end period boundaries respect in this order of increasing priority:
-
The start period and end period take the current year. -
The start period and end period take the default boundaries config settings, if available. -
The start period and end period take the data availability, if available. -
The start period must always be smaller or equal than the end period.
The initial start and end period selection respects in this order of increasing priority:
-
The start period and end period take the above boundaries settings. -
The start period and end period take the default selection config settings, if available and if within the final boundaries settings. -
The start period and end period take the default selection annotation settings, if available and if within the final boundaries settings. -
The start period must always be smaller or equal than the end period.
The issue resolution should thus also address the case when the default time period selection config settings only include the end period but no start period, or no period at all. Configuration documentation to update accordingly once released.