If the temp field is also a character field, it should store the date in mm/dd/yyyy format.
You can’t include keywords or field references within your quotes – they won’t resolve. They’ll be treated as literals. Use “%” + $tempfield$ +”%” The plus will concatenate the string. “%” + $DATE$ + “%” should also work. These assume that you actually have records (rows) that match. You can manually search via the user client (or Mid Tier, if that’s how you access Remedy). The string has to be exact, with any number of variable characters on either side. Mike White EMail [email protected]<mailto:[email protected]> Office 813.978.2192 From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Ddussie Sent: Thursday, April 14, 2011 5:40 PM To: [email protected] Subject: Re: Using Active link to bring data from another form. ** Thank you for responding, Sorry its actually a character field not diary. I did as you suggested, 1. pass the $DATE$ variable to tempfield, so tempfield = 4/14/2011, this did not work. --- Qualification: (Fields1.form2 LIKE "%$tempfield$%") 2. pass the $DATE$ variable to tempfield with % , so tempfield = %4/14/2011%, this did not work. --- Qualification: (Fields1.form2 LIKE "$tempfield$") 3. pass the $DATE$ variable to tempfield with % and " , so tempfield = "%4/14/2011%", this did not work. --- Qualification: (Fields1.form2 LIKE$tempfield$) Its seems that the Like command does not like a variable, what you think? Sincerely, D.Dussie On Apr 14, 2011, at 3:47 PM, "White, Michael W (Mike)" <[email protected]<mailto:[email protected]>> wrote: Are you sure you want to do that? The problem with “%$DATE$%” is that keywords won’t resolve if imbedded within quotes like you’ve shown, but that’s not the only issue. (in another application, you’d use “%” + $DATE$ + “%” instead). Entries in diary fields are timestamped in the format: Thursday, April 14, 2011 3:35:18 PM demo Internally, date/time is stored as EPOC time (number of seconds since 1/1/1970). I’m not sure it wouldn’t treat $DATE$ as unconverted (i.e. it may use mm/dd/yyyy 00:00:00). You could work around this by setting an integer field before your Set Fields and using it in your Set Fields If instead of $DATE$, but again, I’m not sure you want to. Theoretically an entry would need to have been made at the exact. Entries in a diary field aren’t separate rows/records. I imagine it would return the entire contents of the diary field, and you probably wouldn’t want what you got. Mike White EMail [email protected]<mailto:[email protected]> Office 813.978.2192 From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Ddussie Sent: Thursday, April 14, 2011 2:44 PM To: [email protected]<mailto:[email protected]> Subject: Re: Using Active link to bring data from another form. ** Any hints?... Please Sincerely, D.Dussie On Apr 14, 2011, at 1:23 PM, Ddussie <[email protected]<mailto:[email protected]>> wrote: Hello List, What am I doing incorrectly? ActiveLink Associated Form: Form1 Execute on button Runif Qualification null SetFields Datasource: Server ServerName: test Form Name: From2 Qualification: (Fields1.form2 LIKE "%$DATE$%") ; note Fields1.form2 is a diary field Set the following field to Field1.Form1 = $Status$ This is failing because the embedded qualification cannot translate $DATE$. However, if in form2 in the wut, you execute the command Fields1.form2 LIKE "%$DATE$%", it works Also, I tried creating an active link prior to this, set a char temp field to $DATE$, then pass that variable : (Fields1.form2 LIKE "%$TEMP%") , this fails However, if the date is defined (which we need it the variable), so set to (Fields1.form2 LIKE "%$04/14/2011%"), it works In activelink, DATE command can it be used in this way? Have a great day, D _attend WWRUG11 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_
