In Performance Analytics, how do I resolve the error "Sparse storage format has one field, sys_id"

[Tim Wmson]

When I run PA's out-of-the-box Indicator "Summed duration of resolved incidents"

which uses the script "Incident.ResolveTime.Hours"

which is:

var diff=function(x,y){return y.dateNumericValue() - x.dateNumericValue();};

var hours=function(x,y){return diff(x,y)/(60*60*1000);};

hours(current.opened_at, current.resolved_at)

I get the following error:

Error during JavaScript evaluation java.lang.IllegalStateException: Sparse storage format has one field, sys_id

at com.glide.db.meta.SparseStorage.getValue(SparseStorage.java:70)

at com.snc.pa.dc.Row.getValue(Row.java:34)

at com.snc.pa.dc.Script.evaluate(Script.java:96)

at com.snc.pa.dc.DataCollector.collect(DataCollector.java:191)

at com.snc.pa.dc.DataCollector.collect(DataCollector.java:124)

at com.snc.pa.dc.DataCollector.collect(DataCollector.java:80)

at com.snc.pa.dc.DataCollectorJob.collect(DataCollectorJob.java:123)

at com.snc.pa.dc.DataCollectorJob.execute(DataCollectorJob.java:42)

at com.glide.schedule.JobExecutor.execute(JobExecutor.java:72)

at com.glide.schedule.GlideScheduleWorker.executeJob(GlideScheduleWorker.java:177)

at com.glide.schedule.GlideScheduleWorker.process(GlideScheduleWorker.java:124)

at com.glide.schedule.GlideScheduleWorker.run(GlideScheduleWorker.java:56)

Since it's OOTB I would expect this script to work. What can I modify to get it to work?

[Tim Wmson]

Jessica Ferguson said in Performance Analytics - View the full discussion

---

Hey Tim, I wanted to follow up on this. So I was running Eureka Patch 0, I was talking with the support and dev teams and they informed me that this was a known issue that was fixed in Eureka Patch 1. I upgraded to Eureka Patch 7 Hot Fix 1 and it seems to have fixed my issue.

_____________________________________________

However, we're running Eureka on patch 6

[Jochen Pohle · Accepted solution]

Hi Tim,

this usually indicates that a reference field from the PA configuration is not available on your Incident table. Can you please check if your Incident table has a column called resolved_at?

If this is the case please you need to check your Indicator Sources and Breakdown Sources as well.

Hope this helps,

Jochen