[ARCHIVE] Incorrect transaction dates

Archived 2022.11.20. Content moved to error scenarios and responses.

Question

In a call to Get Transactions for Account, if the oldest-time set by the Accredited Data Recipient (ADR) is set in the future, how should the Data Holder (DH) respond?

What if the oldest-time is before 1 January 2017, or more than 7 years in the past, and the newest-time is after 1 January 2017 or less than 7 years from request date?

What if both the oldest-time and newest-time are before 1 Jan 2017 or more than 7 years ago?

Answer

If either of the oldest-time or newest-time values is outside a supported range, or is set to an impossible date, or the times are in conflict with each other, then a 400 Bad Request with error code urn:au-cds:error:cds-all:Field/InvalidDateTime applies.