Date Field needs to respect fully qualified table name

Issue No: DASH-1402
Created 9/11/2015 2:17:19 PM
Type Bug
Priority Major
Status Closed
Resolution Fixed
Fixed Version 15.4
Description The Date Field in the drop down needs to use fully qualified field names. In a query that joins multiple tables, for i21, that means there could be ambiguous references. Meaning the same field name could exist in multiple tables in the query. when this happens, the fields listed in the selection should befully qualified, example tablename.columnname.   Because of this, bad results can be returned to the dashboard. In the example below, the date field was set to "dtmDatePaid". This caused no rows to be returned. When the Date Field was changed to tblAPPayment.dtmDatePaid, the date range selection worked as expected.   !pastedImage_d43478_0.png! !pastedImage_d43478_1.png! No results shown, even though there IS data for today !pastedImage_d43478_2.png! !pastedImage_d43478_3.png! !pastedImage_d43478_4.png! !pastedImage_d43478_5.png!