Reporting on Problem tasks where Problem Related incident equals critical

[NeilOliver]

Hello,

I need to report against all problem tasks where the parent problem has a Priority 1 - Critical incident within its related lists. Can anyone advise on the best way to do this.

I was hoping to be able to do this without custom reports or database views but thats only as I don't know how to work with these reports.

If anyone can provide advice on what table is best to report from or the best way to produce this data I would appreciate it. I need to be able to discuss all tasks and update in a monthly critical incident action meeting.

Thanks in advance,

Neil.

[PeterWiles]

You can reference related lists when creating a report.

On the filter were you choose the field, scroll to the bottom and click on the "Show related lists".

Now click back into the filter and scroll down to the parent field (or what ever field you use to link to the parent problem record) and click on the "parent -> parent fields" (it's colored blue on mine).

Click back into the filter list. You can now view all the fields on the parent problem table. Scroll down to the priority and choose "Priority 1" or what ever you require.

You can do the same on any list view or referencing fields.

Hope that helps (or I have I miss read the question)

Pete

[NeilOliver]

Hi,

Thanks for that Peter, I tried that approach and can't seem to track down the related list for the incidents affected by the problem. Where would you suggest starting from, The problem task table and working back? Or can you do it the other way and work from the incident table and look Problem records > Problem tasks.

Cheers

Neil.

[PeterWiles]

You would need to know what field is referencing what.

On a 1toM (1 to Many) relationship, the "1" is a reference field on the form. Out of the box, there is a field named "problem". When on the problem form, when you add a related list, you should see one named "Incident -> Problem"

You can always check the table listing where you can see the fields on the table and check what references what.

Pete

[Slava Savitsky]

I am afraid you will not be able to build a report like this without a bit of scripting. It looks like you have two one-to-many relationships here: one problem has multiple problem tasks and multiple related incidents (both displayed as related lists on the Problem form). But with dot-walking you can only drill down into a table that is pointed to by a reference field, not into a related list. There are some ways to work around this limitation though:

Option 1: Create a business rule that will somehow mark Problem records that have at least one critical incident linked to them. You could use a dedicated field for that or a value in an existing choice field. The business rule will need to run every time an incident is linked to a problem and also when priority changes in an incident that is already linked to a problem.

Option 2: In a script include, define a client-callable function that will check if a given problem has any critical incidents linked to it. You can then use this function as a up scripted filter in your report. If you have already upgraded to Dublin, you could even create a dynamic filter option that will leverage your function.

Feel free to reach out to me if you need further help on this.