03-31-2006 01:14 PM - edited 03-13-2019 11:38 PM
I have a site where old (removed) agents still appear on the historical reports. Is there a way to purge them out of the reports?
Chris
Solved! Go to Solution.
03-31-2006 01:55 PM
Bug Id CSCed73068 - Old resources appear in Historical Reporting Client
You can view the Bug Id using the Bug tool id http://www.cisco.com/cgi-in/Support/Bugtool/home.pl.
From DDTS-Release Notes :
When a resource name is changed or deleted, the old name still shows up in the Historical Reporting Client's "Details" tab. Currently, this is a result of a desired function for Historical Reports. However, this causes confusion as when a resource is deleted, the deleted resource still appears in the "Details" tab. A recommended feature enhancement would be to allow a more defined 'sort' of the
resources that appear in the Historical Reporting Client's "Details" tab. Current, all resources (new or old) are lumped into one list window within the client. A better sorting method between 'current/active' and 'old/enactive' resource
would allow for less confusion when running historical reports.
The above bug will be fixed in CRS 4.x.
andy dignan - berbee
03-31-2006 01:55 PM
Bug Id CSCed73068 - Old resources appear in Historical Reporting Client
You can view the Bug Id using the Bug tool id http://www.cisco.com/cgi-in/Support/Bugtool/home.pl.
From DDTS-Release Notes :
When a resource name is changed or deleted, the old name still shows up in the Historical Reporting Client's "Details" tab. Currently, this is a result of a desired function for Historical Reports. However, this causes confusion as when a resource is deleted, the deleted resource still appears in the "Details" tab. A recommended feature enhancement would be to allow a more defined 'sort' of the
resources that appear in the Historical Reporting Client's "Details" tab. Current, all resources (new or old) are lumped into one list window within the client. A better sorting method between 'current/active' and 'old/enactive' resource
would allow for less confusion when running historical reports.
The above bug will be fixed in CRS 4.x.
andy dignan - berbee
03-31-2006 03:09 PM
You can hack the sql stored procedure to do this. Only thing cisco will not support it. But it is really not a big deal
04-01-2006 11:00 AM
Sanjeev,
What would be the stored procedure hack?
04-01-2006 11:30 AM
"To isolate active agents (real ones) use this query on db_cra database:
select * from resource where active=1 and orderInRG=0
To correct the problem, edit the report definition file (ej: "ICD_Agent_Summary_en_us.xml") and change the sentence:
"SELECT distinct resourcename FROM Resource"
for this one:
"SELECT distinct resourcename FROM Resource where active=1 and orderInRG=0"
save the file and re-open the Historical Reporter. "
04-02-2006 07:16 AM
Thanks AGAIN!
Chris
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide