Now that would explain the cause of the error.. The integer converted by the 'Start Date' would then always be less than the integer converted by the $DATE$ if it expands to the date time integer thus returning all the records..
Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Thomas Bean Sent: Tuesday, August 21, 2007 7:17 PM To: [email protected] Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification??? ** Joe, I can't remember the bug number off the top of my head, but there has been a longstanding issue with the use of the $DATE$ keyword in workflow qualifications when used against Date fields. The keyword incorrectly expands to a Date/Time integer value instead of a Date integer value. It works correctly when used in a search qualification in the client, however. The workaround that I would normally recommend is this: 1.. On 'Window Loaded', set a hidden, display-only Date field to the value of $DATE$ (the bug doesn't affect set fields values). 2.. In your workflow qualification (i.e., 'Run If', 'Set Fields If', 'Push Fields If', or table field qualification), replace the $DATE$ keyword with the field reference to the hidden display-only Date field. For example, instead of 'Start Date' <= $DATE$, use 'Start Date <= $zTmpCurrentDate$. 3.. For table fields, make sure the table field is triggered to refresh AFTER the hidden display-only Date field value is set to $DATE$ (you may need to de-select the "Refresh on Entry Change" property). Hope this helps, Thomas ----- Original Message ----- From: Joe D'Souza Newsgroups: gmane.comp.crm.arsystem.general To: [email protected] Sent: Monday, August 20, 2007 11:29 PM Subject: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification??? ** Listers, I am literally pulling my hair over this.. I am on ARS 7.0.1 Patch 003 on Windows 2K3SP2 and MS-SQL 2K5SP2.. I have one data form and another display only form. In the data form among other fields I have a character field called Queue and another Date field (not Date/Time). I have a simple qualification using a Date field in the qualification on a Table field. I copied the qualification below. ('Queue' = $Queue$) AND ('Start Date' < = $DATE$) This returns all the records when the table field is refreshed after having a value of "Test Queue" in the Queue field irrespective of the value of the Start Date in the underlying data form when it should have been returning only 1 record on the table field. On the User Tool however if I search the form using advanced search ('Queue' = "Test Queue") AND ('Start Date' <= 8/20/2007) I get just one record as I should given my data. Is this a known bug with using a Date field on a table fields qualification?? Joe No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.484 / Virus Database: 269.12.1/965 - Release Date: 8/21/2007 4:02 PM _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
