0
Completed

Documentation of supported Date and Timestamp field values in Broker CSV files

Adrian Corston 2 months ago • updated by Matthew Davis (Engineering Manager) 2 months ago 4

Could you please document the supported and recommended Date and Timestamp field values that can be used in Broker CSV connector data files?

Beau says he normally uses yyyy'-'MM'-'dd'T'HH':'mm':'ss'Z' (e.g. "2019-06-01T12:34:56Z").

Affected Versions:
Fixed by Version:

Answer

Answer
Completed

Thanks Adrian. I've added it to our backlog to improve the documentation based on the above comments.

GOOD, I'M SATISFIED
Satisfaction mark by Adrian Corston 2 months ago
Under review

HI Adrian,

Both documentation pages for Date and Timestamp refer to the .Net standards for date format, which is what broker supports. There's no specific recommended approach for the format as it depends on the use case of the implementation.

Do you feel the .net page does not provide the information you're after?

The existing documentation for the CSV connector doesn't mention field types at all.  No best practice for read values, and no mention of which format is used for writing either, for both Date and Timestamp fields. The example on that page only mentions string types - it's not clear that any other types are supported at all.

https://voice.unifysolutions.net/knowledge-bases/7/articles/2869-csv-connector

I'd like to see to see a list of supported about field types, and for Date/Timestamp a recommended best practice format and information about what formats are supported when reading and what format is used when writing to those types to a CSV file using the CSV connector.

Also a mention that Date fields are limited to 0000-00-01 to 9999-12-31 might have helped me to work out why the Broker configuration was erroring when attempting to add 1500 days to 9999-12-31 (but then again, it might not have too :-) ).

Answer
Completed

Thanks Adrian. I've added it to our backlog to improve the documentation based on the above comments.