Millisecond dropping leading zero in date/time filter
Has anyone come across this before? I have a date/time field in SQL Server that contains a value "2017-01-09 14:17:45.017", and this field is used to populate a dropdown filter. However when the report SQL is parsed it drops the leading zero off the millisecond component of the time to come up with this "2017-01-09 14:17:45.17" which of course will result in no rows returned. Is this a bug or a configuration problem on my end?