As I see, you have to options: 1.- Figure out an SQL sentence that provides this information, (You can use the audit). This sentence will be a high CPU and Mem consuming, since the only solution I see is to create a subquerys at the audit to see which log recors are about priory and when this records mean a higher value or lower value than the current value. Another option would be to get the first log value, since it will contain the initial priority. Then you can create a derived table at the universe designer anduse it. Every time you get a report with some dimension of this table it will take long.
2.- Create a new field at HPD:Help Desk that reports the initial priority value, populated at submit. So you can compare this value with the current one to see if goes up or down. Regards, Jose Huerta http://theremedyforit.com/ On Tue, Mar 20, 2012 at 05:15, andrew tokarz <andrew_tok...@yahoo.com>wrote: > ** > Curious if anyone has tried to create a report using BMC Analytics where > you track the amount of times the priority is upgraded or downgraded in an > incident. > > So for 25000 incidents how many times were the incidents upgraded from: > > -Low to Critical > -Low to Medium > -Medium to High > -High to Critical > > or downgraded from: > > -Critical to Low > -Critical to Medium > -Medium to Low > > Audit log tracks when a priority is changed but its not in a single field > to report on. Its in a text/diary field with 40 other fields. You would > have to somehow parse this out. > > > Is there a simple way to do this in Analytics? Or would it be best if you > create a supporting table that is updated to track priority changes when > they occur. > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
