specs icon indicating copy to clipboard operation
specs copied to clipboard

Published 20 hours ago • verified publisher icon reconciliation-api

Unify the syntax for property values in reconciliation queries and data extension responses

Open wetneb opened this issue 3 years ago • 1 comments

The way we serialize our property values in JSON is different depending on the context: see the JSON schemas for reconciliation queries and for data extension responses.

It would be nice to unify this.

wetneb avatar Jul 27 '22 11:07 wetneb

Moreover, there is currently an inconsistency in the specs (links are to the 0.2 specs, but we have the same problems in the current draft):

  • the Property values section declares that properties are one of the following:

    • A string;
    • A boolean;
    • An integer;
    • A floating-point value;
    • An entity.

  • the schemas for the data extension response do not include an option for booleans, and include an option for null values and dates, which are not mentioned above.

wetneb avatar Oct 08 '23 07:10 wetneb