1
Hello, this seems a bit silly to open this as an idea as it's small but I have found an inconsistency in the date time objects that are being returned by the BC API.
When a record has been modified, the date time that is returned will look something like this: 2020-11-20T00:58:41.493Z. Critically, the millisecond value is specified to three digits. However, on records where there is no last modified date time to return, the API appears to return a generic empty date that looks like this: 0001-01-01T00:00:00Z. The main difference is that the empty date does not have a millisecond value. This is causing issues for my system because of the inconsistent date time formats between records.
Thank you.
When a record has been modified, the date time that is returned will look something like this: 2020-11-20T00:58:41.493Z. Critically, the millisecond value is specified to three digits. However, on records where there is no last modified date time to return, the API appears to return a generic empty date that looks like this: 0001-01-01T00:00:00Z. The main difference is that the empty date does not have a millisecond value. This is causing issues for my system because of the inconsistent date time formats between records.
Thank you.
STATUS DETAILS
Needs Votes
Comments
According to the ISO 8601 format: "There is no limit on the number of decimal places for the decimal fraction".
So your system has to handle this.
Category: Development
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team