February 07, 2010, 10:47 PM
<ABHINAV BALI>Getting Error in Setting up Alert
Hi Everyone,
I have set up an alert such that when one of the measure goes from green to yellow, it fires an alert and pmfadmin get an email in outlook express… request is going to reportcaster but when i look into log, it shows error:
User: pmfadmin
Procedure: J14qlpt55708
Schedule ID: S14qlilb4802
Start Time: 2010-02-08 02:28:01 PM
End Time: 2010-02-08 02:28:04 PM
Schedule Executed Due To NEXTRUNTIME
Starting task: app/alert
Connecting to server EDASERVE with execution id admin
Error running alert app/alert from MRE:EdaExcp Eda code 3 subcode: 0 xopen: S1000 THE FIELDNAME IS NOT RECOGNIZED: SHOW_CURR_ACTUAL
Task error:EdaExcp Eda code 3 subcode: 0 xopen: S1000 THE FIELDNAME IS NOT RECOGNIZED: SHOW_CURR_ACTUAL
No report to distribute.
Not sure why its not recognizing the field name...
Thanks for help.
Abhi
February 08, 2010, 08:13 AM
Bob Jude FerranteYou are running 5.2. Beta, correct?
February 08, 2010, 03:07 PM
<ABHINAV BALI>Yes. But wondering why?
February 08, 2010, 03:13 PM
Bob Jude FerranteOf course. But we can't work from just a repro without any detail about what release.
It's most probably a bug in the Beta. That's why it is a Beta.
We'll make sure production doesn't have the bug.
thanks
February 09, 2010, 05:24 PM
Bob Jude FerranteHi Abhinav--
We can't repro this in our test environments so we're assuming we don't have the right specifics.
So that we can track this and try to resolve it, can you get your info to IBI-CSS and open a case with them, so we can track all the details of it? You'd need to provide the repro steps you used to set up the alert, etc, including what report you were having the alert run on fire, the conditions, the test DB you were using, etc.
thanks!
February 10, 2010, 06:03 PM
<ABHINAV BALI>I will set up a case and will let you know.
Thanks
Abhi
February 11, 2010, 07:04 PM
<ABHINAV BALI>Hi Bob,
I have now set up a IBI Case #60412555 .
Thanks
Abhinav
February 11, 2010, 07:10 PM
Bob Jude FerranteThank you. We got your repro - excellently and expertly prepared - and have now found and fixed the problem.
Thanks to you there's one bug that won't be happening in 5.2.1.
Much appreciated.
The PMF team