SSRS Bug: Choose new target for linked report offers no reports
Install and configure SQL Server Reporting Services 2016SP1CU7 (mine was a Migration from 2008R2SP3, but an empty one should do). Upload a 'master' Report and create a link to it. Delete the 'master' and re-upload it. The link is now orphaned as expected.
In previous Versions, one could re-map the link to a different master without losing parameter configuration. It had problems with hidden folders, but allowed to enter a path explicitly by hand.
2016 pops up a selector box (aggravatingly using tiles no matter how often I dell it I want lists), which allows browsing folders, but all folders Show up empty, and Manual path entry is not offered. A manual update to the catalog table leads to a link object showing the correct master but running into some fatal error upon execution. The Stored procedures collection has nothing fitting sounding like it might do the Job, and I searched an hour for socumentation on the current web service to no avail.
So, how can one fix linked reports without "resorting to violence" (aka delete, recreate, re-enter Parameters)?
Just stumbled on this today, and found a workaround, without "resorting to violence", using T-SQL.
Query below selects all linked reports, with their RDL reports:
link.Path AS LinkName
, link.ItemID AS LinkId
, rdl.Path AS LinkedToName
, rdl.ItemID AS LinkedToId
FROM ReportServer.dbo.Catalog AS link WITH (NOLOCK)
LEFT JOIN ReportServer.dbo.Catalog AS rdl WITH (NOLOCK)
ON link.LinkSourceID = rdl.ItemID
-- 2 = RDL report.
AND rdl.Type = 2
-- 4 = Linked report.
WHERE link.Type = 4
-- Add additional filters, should you need.
Update below, would update the linked report to where you need it to point to:
-- Set LinkSourceID to the correct RDL ID.
SET LinkSourceID = 'D652AEF0-E843-76B2-99EA-073AAAA6BD81'
-- Set ItemID to the linked report's ID.
WHERE ItemID = 'CB32903E-43D2-488C-9DC1-78ECCCC7C56F'
Not pretty, or easy, but works.
Hope this helps.
Any news? This makes making report changes very frustrating, because after amending the report we have to reconfigure the entire report setup on the portal (including subscriptions, security, all linked reports, etc.) in order to make the change available to the end users.
Carlos Pérez commented
Any news on this issue?