Database Reference
In-Depth Information
ASU.DisplayName AS [AssignedTo]
FROM
MT_System$WorkItem$Incident I WITH (NOLOCK)
LEFT OUTER JOIN Relationship AFR WITH (NOLOCK) ON
I.BaseManagedEntityId = AFR.SourceEntityId
AND AFR.RelationshipTypeId =
'DFF9BE66-38B0-B6D6-6144-A412A3EBD4CE'
AND AFR.IsDeleted = 0
LEFT OUTER JOIN MT_System$Domain$User AFU WITH
(NOLOCK) ON
AFR.TargetEntityId = AFU.BaseManagedEntityId
LEFT OUTER JOIN Relationship ASR WITH (NOLOCK) ON
I.BaseManagedEntityId = ASR.SourceEntityId
AND ASR.RelationshipTypeId =
'15E577A3-6BF9-6713-4EAC-BA5A5B7C4722'
AND ASR.IsDeleted = 0
LEFT OUTER JOIN MT_System$Domain$User ASU WITH
(NOLOCK) ON
ASR.TargetEntityId = ASU.BaseManagedEntityId
LEFT OUTER JOIN LocalizedText TClassification ON
I.Classification_00B528BF_FB8F_2ED4_2434_5DF2966EA5FA
= TClassification.LTStringId
AND TClassification.LanguageCode = 'ENU'
AND TClassification.LTStringType = 1
WHERE
Id_9A505725_E2F2_447F_271B_9B9F4F0D190C =
@IncidentID
9. When prompted to
Enter Data Source Credentials
, select
Use the current Win-
dows user
or type the password for the service account and click on
OK
.
10. Notice that the
@IncidentID
placeholder we used in the query we just added to
our dataset appears under
Parameters
in the
Report Data
area. Report Builder
automatically created a corresponding report parameter to allow
incident ID
to
pass to our report. Expand the
Parameters
node in Report Builder and make sure
the
IncidentID
parameter has been added.
11. In Report Builder, in the
Design
area, replace the
Click to add title
with
Incident Details
.
