So it seems like the table itself may not be the issue, though i'm not
entirely sure. What I setup was a display form with two date/time fields
for input, a character field for the EXTERNAL(query), and the table field
pointed to one of our most populated forms.
What I found out was this:
I created workflow that takes the two date fields and puts them into the
character field so the resulting string looks like this:
'Create Date' >= "8/3/2010 8:00:00 AM" AND 'Create Date' <= "8/5/2010
11:00:00 AM"
In my table qualification I have: EXTERNAL('Character Field')
When I refresh the table, the table searches and displays results as if the
following query is ran:
'Create Date' >= "8/3/2010 9:00:00 AM" AND 'Create Date' <= "8/5/2010
12:00:00 PM" <-- Notice the one hour difference
Now I replaced the qualification for the table: EXTERNAL('Character Field'),
with the actual qualification I'm trying to run:
'Create Date' >= "8/3/2010 8:00:00 AM" AND 'Create Date' <= "8/5/2010
11:00:00 AM"
When I refresh the table field, the values now accurately display from
8/3/2010 8:00:00 AM to 8/5/2010 11:00:00 AM. "Hmm," I think to myself,
"There must be an issue with searching with dates using the EXTERNAL
function."
I now replace the qualification string for the table with:
('Create Date' >= $Date/Time Field$) AND ('Create Date' <= $Date/Time
Field2$)
Therein by taking EXTERNAL() completely out of the loop. I enter "8/3/2010
8:00:00 AM" into $Date/Time Field$ and "8/5/2010 12:00:00 PM" into
$Date/Time Field2$ and refresh the table.
The results show correct!! The date/time span return match the search
criteria accurately. So there seems to be an issue when searching table
fields with date ranges using the EXTERNAL() function.
Not sure if this was mentioned before on the list, sorry if it was, this bug
has been running me and my QA team around in loops.
Just thought I would share. Thanks for listening :D
On Thu, Aug 5, 2010 at 3:35 PM, Robert Halstead <badbee...@gmail.com> wrote:
> Hey all,
>
> We're seeing a discrepancy when displaying data in a table field. If the
> table field is searching a date range of tickets, the table field seems to
> display tickets that are an hour ahead. It seems the client takes the
> date/time in the date/time fields and applies +1 hour to them and then
> returns the result of that search.
>
> Searching the same date range on the form itself returns the proper
> listing.
>
> This behavior doesn't exist with the mid-tier. Performing the same actions
> in the mid-tier, the results are what is expect with both the table and the
> form displaying the same search results. Only in the client does it seem to
> differ.
>
> This seems to be an issue with the timezone and table fields. I was
> wondering if anyone else has been incurring this as well?
>
> AR Server 7.5 Patch 004
> Mid-Tier 7.5 Patch 004
> WUT 7.5 Patch 004
>
> Let me know if more information is needed. I thought I'd hit up the list
> before I created a ticket with BMC.
>
> --
> "A fool acts, regardless; knowing well that he is wrong. The ignoramus acts
> on only what he knows, but all that he knows.
> The ignoramus may be saved, but the fool knows that he is doomed."
>
> Bob Halstead
>
--
"A fool acts, regardless; knowing well that he is wrong. The ignoramus acts
on only what he knows, but all that he knows.
The ignoramus may be saved, but the fool knows that he is doomed."
Bob Halstead
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
