{"id":1537,"date":"2013-06-16T14:34:27","date_gmt":"2013-06-16T12:34:27","guid":{"rendered":"http:\/\/www.itidea.nl\/?p=1537"},"modified":"2013-06-16T14:35:03","modified_gmt":"2013-06-16T12:35:03","slug":"summarylinks-webpart-and-outgoing-links","status":"publish","type":"post","link":"https:\/\/www.itidea.nl\/index.php\/summarylinks-webpart-and-outgoing-links\/","title":{"rendered":"SummaryLinks webpart and outgoing links"},"content":{"rendered":"

At a client I worked on migrating content from Tridion to SharePoint 2010. Data included links that had to be migrated to links in a SummaryLinks webpart.
\nFor another feature of the project the outgoing links of a page were used to do something with it. After migrating the content to a SummaryLink webpart the code of the feature mentioned there were no outgoing links on the page. The SharePoint Content and Structure can show Related Resources on a page, which includes outgoing links. This overview didn’t show the links either.
\n\"\"<\/a><\/p>\n

Figure 1 – SummaryLinks webpart with some links<\/h5>\n

\"\"<\/a><\/p>\n

Figure 2 – No outgoing links shown in the overview<\/h5>\n

After editing the page by making some changes to the SummaryLinks webpart the outgoing links started to appear in the Content and Structure overview.<\/p>\n

\"\"<\/a><\/p>\n

Figure 3 – Outgoing links are shown<\/h5>\n

At this point is was obvious SharePoint did something to the webpart when modifying it from the UI, which was missing or didn’t fire when adding the webpart with links from code.<\/p>\n

Time to start SharePoint Manager to see what’s going on by comparing the settings of two summarylinks webparts: one which was added programmatically and one which was fully configured by the UI.<\/p>\n

\"\"<\/a><\/p>\n

Figure 4 – Webpart on the left was added programmatically, on the right configured by UI<\/h5>\n

The first thing I did was comparing the xml of the two webparts. There were some changes, but these were related to the fact the webparts were placed in another webpart zone, had another title and another link set.<\/p>\n

The next thing was to put two windows in SharePoint Manager next to each other and do some comparison of the properties set. After some quick scrolling I noticed the ManagedLinkHash was populated with a GUID at the webpart which was configured from the UI and this property was empty at the webpart which was programmatically added to the page. Besides the difference at the ManagedLinkHash property also the ManagedLinks collection was different between the two webparts: The collection was empty for the webpart added programmatically to the page.
\n\"\"<\/a><\/p>\n

Figure 5 – Properties of webpart (configured in UI) in SharePoint Manager<\/h5>\n

\"\"<\/a><\/p>\n

Figure 6 – Properties of webpart (added programmatically) in SharePoint Manager<\/h5>\n

These two properties are internally used by SharePoint to determine changes in the link targets of the SummaryLinks webpart.
\nThe ManagedLinkHash is a hash of the saved ManagedLinks links and is used to quickly determine if the ManagedLinks have been modified by the system since the last time that they were saved, quite neat actually.
\nThe ManagedLinks property stores the url’s of the SummaryLinks (stored in the SummaryLinkStore property) so they can be updated by the Web Part framework if the link targets move within the SharePoint site.
\nThe code to add the links to the SummaryLinks webpart including setting the ManagedLinks property:<\/p>\n

\r\nSummaryLink link = new SummaryLink("IT-Idea");\r\nlink.LinkUrl = "http:\/\/www.itidea.nl";\r\nSummaryLink linkwithinSP = new SummaryLink("Lorem txt");\r\nlinkwithinSP.LinkUrl = "http:\/\/sp2010\/Documents\/lorem.txt";\r\nSummaryLinkFieldValue sumlinks = new SummaryLinkFieldValue();\r\nsumlinks.SummaryLinks.Add(link);\r\nsumlinks.SummaryLinks.Add(linkwithinSP);\r\nwp.SummaryLinkValue = sumlinks;\r\n\r\n\/\/add the links to the managedlinks array for automatic link updates by SharePoint\r\nforeach (SummaryLink item in sumlinks.SummaryLinks)\r\n{\r\n wp.ManagedLinks.Add(item.LinkUrl);\r\n}\r\n<\/pre>\n
The ManagedLinkHash is generated of the links added to the SummaryLinks webpart.<\/p>\n
The result on the page stays the same, but the Content and Structure and SharePoint Manager will display the links correctly:<\/p>\n
\"\"<\/a><\/p>\n
Figure 7 – Related resources overview in Content and Structure shows links<\/h5>\n
\"\"<\/a><\/p>\n
Figure 8 – Properties in SharePoint Manager show links<\/h5>\n
When the document will be moved to another library:
\n\"\"<\/a><\/p>\n
Figure 9 – Moving a document to another location<\/h5>\n
The ManagedLinkHash, ManagedLinks and the SummaryLink will be instantly updated.
\nSummaryLink change can be seen in the Content and Structure overview:
\n\"\"<\/a><\/p>\n
Figure 10 – Link changes shown<\/h5>\n
The changes to the ManagedLinkHash and ManagedLinks properties can be seen in SharePoint Manager:
\n\"\"<\/a><\/p>\n
Figure 11 – SharePoint Manager view<\/h5>\n
Summary<\/h3>\n
Sharepoint keeps administration about the linked objects in the SummaryLinks webpart. Make sure you do to!<\/p>\n","protected":false},"excerpt":{"rendered":"
At a client I worked on migrating content from Tridion to SharePoint 2010. Data included links that had to be migrated to links in a SummaryLinks webpart. For another feature of the project the outgoing links of a page were … Read More »<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[20,42],"class_list":["post-1537","post","type-post","status-publish","format-standard","hentry","category-sharepoint-2010","tag-c","tag-sharepoint-2010"],"_links":{"self":[{"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/posts\/1537","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/comments?post=1537"}],"version-history":[{"count":11,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/posts\/1537\/revisions"}],"predecessor-version":[{"id":1561,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/posts\/1537\/revisions\/1561"}],"wp:attachment":[{"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/media?parent=1537"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/categories?post=1537"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/tags?post=1537"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}