It appears to be ok to me (a minor change, takes care of the date error), but that area is new to me, so I'd like to hear an opinion from Tim, Phil, or anyone else more familiar with that area.
One question in the file changes:
Line 352, the concat of the part number with the description?
(12-21-2017, 04:25 AM)TurboPT Wrote: It appears to be ok to me (a minor change, takes care of the date error), but that area is new to me, so I'd like to hear an opinion from Tim, Phil, or anyone else more familiar with that area.
One question in the file changes:
Line 352, the concat of the part number with the description?
I removed that from my instance and keep the Supplier/Vendor PN separate.
I may likely have to keep the original form of that specific line to avoid surprises, unless others feel that the change is ok.
(though that being said, as the change is so minor it may get committed anyway, as it may likely go unnoticed )
(12-21-2017, 06:47 AM)TurboPT Wrote: Oh, I see, sorry I had that backwards.
I may likely have to keep the original form of that specific line to avoid surprises, unless others feel that the change is ok.
(though that being said, as the change is so minor it may get committed anyway, as it may likely go unnoticed )
Yes. To avoid any surprises best to leave as is. Some may expect and/or require it to be presented in that fashion.
I have not yet committed the file, as I was investigating more around that area.
The suggested fix DOES appear to fix the case when there is an actual quotation and order number combination, but then using the Outstanding Sales Orders/Quotations link with the order number, and 'Orders_Only' can generate the similar date error as shown below: [the date error message is generated by function: ConvertSQLDateTime()]
The query does return 1 row, though ALL fields are NULL: (as also shown in the debug textarea above)
...and running the explain on that query gives:
Any ideas on why we would not get 0 rows instead of 1 row that has all fields NULL to avoid this issue? As it's not just the dates, but the output table (below the error messages) appears to be pointless with null information, but output because 1 row was found.
I am using Server version: 10.1.21-MariaDB ... does anyone see different behavior on MySQL ?