Show Service Request properties in Manual Activity Grid
Best Answer
-
Ilias_El_Taghadouini Customer IT Monkey ✭Hi Geoff,
I was able to create a SQL table widget which exactly shows me what I need.
Here's the SQL query:SELECT TOP 25 wi.WorkItemId, wi.Title, wi.AssignedUser, wi.ParentWorkItemId PARENT_ID, sr.AffectedUser PARENT_AFFECTEDUSERFROM [WorkItem] wi LEFT JOIN [Enumeration] enum ON enum.EnumerationID = wi.TierIdINNER JOIN [WORKITEM] sr ON sr.WorkItemId=wi.ParentWorkItemIdWHERE wi.ClassId = '7AC62BD4-8FCE-A150-3B40-16A39A61383D'AND wi.StatusId = '11fc3cef-15e5-bca4-dee0-9c1155ec8d83'
I had spaces in the column headers ("Parent ID" and "Parent Affected User") which didn't work in the dashboard designer so be careful with that
Regards,
Iliass5
Answers
Its possible to show the Parent WorkItem ID by making a view in the Console using the type projection containing this relationship and then promoting to the portal.
However, if the MA is withing a Parallel or Sequential activity, then this is the parent so you will see this ID instead.
There maybe something you can do with a SQL table widget where the query can recuse up to find the top parent, I'm going to have a play and see what I can come up with.
Geoff
Thanks for the pointers, I'll try the SQL table widget too and keep you updated
I was able to create a SQL table widget which exactly shows me what I need.
Here's the SQL query:
I had spaces in the column headers ("Parent ID" and "Parent Affected User") which didn't work in the dashboard designer so be careful with that
Regards,
Iliass
Hi @Ilias_El_Taghadouini,
Are your users using IE11 by any chance?
For some reason IE11 would cache the query results and the user would have to close the browser or clear the local cache to force it to refresh.
We've had an item added to the Cireson backlog to force the dashboard results to use No Caching for this scenario.
Alternatively, Firefox doesn't have this issue, and in IE11, users can change their "Check for newer versions of the webpage" to "Every time I visit the webpage"; "Automatically" did not work.