Welcome to the Consumer Data Right Support Portal

Check out our guides, browse through our FAQs, and post your own questions for Support.

New to the Consumer Data Right? Learn more

BankingCreditCardAccount for new credit cards Follow

Comments

3 comments

  • Avatar
    Justin

    Is an empty string a "suitable default", or is the expectation that any "suitable default" would validate as a DateString?

    Does this apply? https://cdr-support.zendesk.com/hc/en-us/articles/900002616823-Mandatory-Fields-with-no-value-present

    0
    Comment actions Permalink
  • Avatar
    Jarryd Judd

    Thanks for the question Justin I've raised a ticket #1413 within the CDR Support Portal. 

    I will loop back and update this thread when it is answered.

    -Jarryd

    0
    Comment actions Permalink
  • Avatar
    Jarryd Judd

    Hi Justin

    An empty string is not itself a valid DateString so it couldn't be used as a default. The "empty string" imparts specific meaning which is defined in the Payload Conventions (and copied below). 

    Empty/Null Fields

    • An empty field (ie. a field that is not present in a payload) will be considered equivalent with a field that is present with a null value.
    • An empty string (“”) is not considered to be equivalent to null.
    • A Boolean value of false is not considered to be equivalent to null. Optional Boolean fields, by implication, have three possible values: true, false and indeterminate (ie. null).

    Is there a specific API response that is off issue with returning a valid date string?

    (Same answer as given on Ticket 1423.

    Thanks,

    -Jarryd

    1
    Comment actions Permalink

Please sign in to leave a comment.