Wrong TimeRange in actual content constraint if the TIME_PERIOD is not a last dimension in a DSD
When TIME_PERIOD is not the last dimension in a DSD, then TimeRange in the actual content constraint that is generated after the data upload is wrong, having 1900-01-01T00:00:00 in both Start and End periods
common:TimeRange>
<common:StartPeriod isInclusive="false">1900-01-01T00:00:00</common:StartPeriod>
<common:EndPeriod isInclusive="false">1900-01-01T00:00:00</common:EndPeriod>
</common:TimeRange>
Example: NSI v7.11.1.0 http://nsi-reset-qa-oecd.redpelicans.com/rest/dataflow/OECD/DF_HEALTH_SERVICES/1.0.0?references=all
Edited by Anastassia Samsonova