Hi there,
Previously, when I imported datetime minvalue from BC (0001/1/1) into DynamicWeb it would end up as 0001/1/1 in the database also (I am using datetime2 as the column type which should support this). After upgrading to Dynamicweb 9.16.4, these values now end up as 1753/1/1 which is the min value for datetime in SQL Server. That broke a couple of things in my solution in places that assumed 0001/1/1 as the value. I think it's from a code change on 10/18/2023 that adds this to ColumnMapping.cs
private DateTime AdjustDateTime(DateTime dateTime)
{
DateTime theDateTime = dateTime;
if (theDateTime < SqlDateTime.MinValue.Value)
{
theDateTime = SqlDateTime.MinValue.Value;
}
else if (theDateTime > SqlDateTime.MaxValue.Value)
{
theDateTime = SqlDateTime.MaxValue.Value;
}
return theDateTime;
}
Should this code be updated to support datetime2 and return 0001/1/1 as the min value instead?
Imar
