Received via tech support regarding the change in reporting fields between v10 and v11

I remember that the Issue 1, Issue 2, Issue 3 and Issue 4 are variables that I declared to break up the Issue field to report different category levels. How is it now with the version of helpmaster? Is there fields that I can use to report different level of call issue type?

The Issue1, Issue2 etc fields are no longer part of the base reporting views.  They have been replaced with the complete field simply called Issue.

To isolate each individual level of the Issue hierarchy, you can do one of the following.

1. Create a formula within Crystal Reports to chop up the "Issue" field into it's individual components.  Often, just the first level of the issue hierarchy is used to get a "Top Level" code.  In a Crystal Report formula, this would be achieved using a formula like this.

If Instr(1,{Command.Issue},">")>0 Then
    Formula = Left({Command.Issue},Instr(1,{Command.Issue},">")-1)
Else
    Formula = {Command.Issue}
End If

2. Create a view in the database that returns each level and then join this view to your reporting view / command that is being used in Crystal Reports.  The old view definition for HelpMaster v10 and prior was this

CREATE VIEW [dbo].[qryJobIssue]
AS
SELECT tblIssues_1.pkID, tblIssues_1.Caption AS Issue, tblIssues_2.Caption AS Issue1, tblIssues_3.Caption AS Issue2, tblIssues_4.Caption AS Issue3,
 tblIssues_5.Caption AS Issue4,tblIssues_1.IsDeleted
FROM dbo.tblIssues tblIssues_4 LEFT OUTER JOIN
 dbo.tblIssues tblIssues_5 ON tblIssues_4.SelfLink = tblIssues_5.pkID RIGHT OUTER JOIN
 dbo.tblIssues tblIssues_1 LEFT OUTER JOIN
 dbo.tblIssues tblIssues_2 ON tblIssues_1.SelfLink = tblIssues_2.pkID LEFT OUTER JOIN
 dbo.tblIssues tblIssues_3 ON tblIssues_2.SelfLink = tblIssues_3.pkID ON tblIssues_4.pkID = tblIssues_3.SelfLink

Note however that this SQL will return the issue hierarchy in reverse order due to the way the self-linking fields in the database works.  To get it into the right order, you can either re-write the SQL, or do it via a Crystal Reports formula as was the case in v10 of HelpMaster.

Crystal Reports formula "Issue" using Visual Basic syntax.

Dim strIssue As String

if not isnull({qryJobIssue.Issue4}) then
    strIssue = strIssue & {qryJobIssue.Issue4} & " > "
end if
if not isnull(qryJobIssue.Issue3}) then
    strIssue = strIssue & {qryJobIssue.Issue3} & " > "
end if
if not isnull({qryJobIssue.Issue2}) then
    strIssue = strIssue & {qryJobIssue.Issue2} & " > "
end if
if not isnull({qryJobIssue.Issue1}) then
    strIssue = strIssue & {qryJobIssue.Issue1} & " > "
end if
if not isnull({qryJobIssue.Issue}) then
    strIssue = strIssue & {qryJobIssue.Issue} & " > "
end if

' Cleanup trailling " > "
if len(strIssue)> 3 then strIssue = left(strIssue,len(strIssue)-3)

formula = strIssue