*** Public Service Announcement ***
I’m not sure which version the change happened in, but when we upgraded from 10.1.400 to 10.2.300, we found that the datatype of the GLJrnDtl.PostedDate type changed from {date} to {datetime}
- If you have any BAQs that used that field for GroupBy, they won’t work as they did when the field was just a {date}.
For example:
I made a BAQ of just the GLJrnDtl table, with the fields:
This should have unique values in the Jrnl Num row as all journal lines post “at the same time”, and they are grouped by the PostedDate field. But as you can see in the pict below, there are two distinct rows for Journal Num’s 1033 and 1035. Even though they show the “same” values for PostedDate.
Changing the format of the PostedDate row from {datetime} to {datefulltime}, yeilds the issue:
A time diff of just 17 milliseconds and those records no longer group together.
- If you have a BAQ Report with an Option field with an “=” operator, you’d have to enter the exact date and time (including milliseconds) to select those records. Selecting all the records for a specific Date is no longer trivial. I resolved this by adding a calculated field to my BAQ that I just
CONVERT(Date, GLJrnDtl.PostedDate)
then have my Report Optional tied to that field.
=========