Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Issue with listview report data

SA-9425

Summary



ListView is being used to generate reports from an external database. Both PRPC application database and external application database are located in the US.

There is an agent which runs everyday at 11:30 PM EST to generate the report. The 'Date' is mapped to "Today" in the Content tab of the ListView. The issue is, the TODAY parameter returns the date in GMT format and thus tries to get the data from next day. Ideally, it should populate the date from the agent's timezone which is configured as EST.

Error Messages



Not Applicable. 

Steps to Reproduce



1. Create a ListView and Filter on "Today" as criteria.
2. Schedule an Agent to use US Eastern timezome
4. Set the Agent to run at 11:30 PM EST.

Root Cause



PRPC stores time in GMT format in the database. When the scheduler is run at 11:30 PM EST , it gets the result adding GMT+5.

Resolution



Setting the Date in database level to query using EST timezone corrected the behavior.

Another Local change has been shared to try out:


Customize the 'Context' activity to set a timezone for batch requestor page.

Sample Java code:

PRRequestor r = tools.getRequestor();
ClipboardPage rPage = r.getRequestorPage();
rPage.putString(“pxReqLocale”,”en_US”);
rPage.putString("pyUseTimeZone"," America/xxxxxx ");

Published June 12, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us