**SLSO is a self-hosted organization**
I followed the steps in this post from several years ago. In the template/report, I went to the Reports menu at the top, and clicked on Report Properties. Clicked on the "Code" tab at the left, and inserted this
Function GetTessituraLink(resource as String, id as Long) As String
If NOT Report.Globals!RenderFormat.IsInteractive Then
RETURN Nothing
End IF
If NOT (len(resource) > 0) OR id < 1 Then
End If
RETURN Report.Globals!ReportServerUrl & "?/Tessitura/Links/" & resource & "&Id=" & id
End Function
Then I added this to the customer number text box via Action>>Go to URL:
=globals!ReportServerUrl & "?/Tessitura/Links/Constituent&Id=" & Fields!customer_no.Value
For me, and for other users it is working as expected, but I have one user who is getting an error message.
Any ideas on why this is occurring and how to fix it?
Ashley Elliott
Database Administrator
St. Louis Symphony Orchestra
314-286-4198
ashleye@slso.org
To be clear, using the Code tab to add the GetTessituraLink function to your report (or better yet, keeping it in your report template), is supposed to be a convenience so that in the Action box, you only need to type =Code.GetTessituraLink("Constituent", Fields!customer_no.Value). If you write out the entire string expression yourself, you don't need to put anything in the Code tab at all.
Remember that these links only work within the Tessitura Client's embedded SSRS viewer. If someone is using the TessituraWeb (TOTG) application, for example, they will get an error when they attempt to click that link. It's because the URL isn't actually "real" -- it gets captured by the Tessitura application before the embedded browser window attempts to fetch it, and is parsed by Tessitura to display the requested window using internal Client application functionality. Perhaps that is what your one user is running into.
Turns out this may have been user error, but I am glad I made this post because you explained the concept to me, whereas I was just copying parts of that post and things in existing reports built by my predecessor to make it work. It is always useful to have an understanding of what I am doing and why. Thank you!
Ashley