Release 1.0.2 (2020-07-17)
  • 24 Aug 2023
  • 4 Minutes to read
  • Contributors
  • Dark
    Light
  • PDF

Release 1.0.2 (2020-07-17)

  • Dark
    Light
  • PDF

Article summary

Release 1.0.2 (2020-07-17)

Fix: Correct "search sites" failure when unsupported site templates are encountered

Update code to use inclusive rather than exclusive list of supported site templates (Issue 1083)

Tag Manager previously queried for all site templates excluding from it's supported list, and when unaccounted for templates were encountered an error was thrown. This change modifies the query to a predefined list of supported templates intead.


Enhancement: Add Hub Site Title search functionality.

Update code to allow users to search for sites associated to a Hub Site, by the Hub Site's Title (Issue 1089)

Tag Manager could search for site collections by their URL or Title, but could not search for Hub related sites. A new search box has been added to allow the searching for the Hub Site Title to find related sites. Support for searching by Hub ID may be added in a future release.


Fix: Correct lack of Page View Hits when transitioning between some pages

Update code to properly fire Page View event when moving between Single Page App behavior like pages in Modern sites (Issue 1088, 1140)

Modern sites often use Single Page App (SPA) behavior for page transitions, i.e. moving from the Home Page to an Article does not refresh the browser and simply changes the content displayed in the DOM. This update corrects behaviour using the "navigatedEvent" callback within the SharePoint Framework to properly reset the tag and fire a Page View event when a SPA transition occurs.


Fix: Correct ability to replace SP Tag methods with alternative versions.

Update code to properly support SP Plugins "overlays" object functionality (Issue 1090)

In some cases customers need to customize behavior of the SP tracking plugin for their environment. This may require editing some of the main methods used to collect data. The SP plugin's "overlays" feature allows users to define alternative function definitions to replace the default definitions. Tag Manager was improperly interpretting new definitions as Strings and did not properly replace the function definitions.


The following are fixes/enhancements to the underlying code shared by all SharePoint products and not specific to SharePoint Tag Manager.


Fix: Correct Modern Search related behavior

Update code to correct lack of Search related data (Issues 976, 975, 1053, 1055, 1056, 1057, 1060, 1061, 1063, 1065, 1066, 1192, 1193)

Changes in SharePoint Online modern view "Search Results" pages resulted in loss of proper tracking of search interactions. This primarily affected the count of the number of results (which was showing as 0 for all searches) and double hits on search result clickthroughs. Search related code was refactored in its entirety to be more resiliant to future changes and to improve tracking overall.


Fix: Correct Modern Suggested Search related behavior

Update code to correct data related to Suggested Search item clickthroughs (Issues 1054, 1064, 1196, 1197, 1198, 1199, 1200)

Changes in SharePoint Online modern view "Suggested Search Results" resulted in loss of proper tracking of search interactions. Search related code was refactored in its entirety to be more resiliant to future changes and to improve tracking overall.


Fix: Correct Modern Enterprise Search (/sharepoint.aspx) related behavior

Update code to provide support for Modern Enterprise Search activity (Issues 1129, 1184, 1185, 1186, 1187, 1188, 1189, 1190)

SharePoint Online provides a Modern experience for the Home Page with a /_layouts/15/sharepoint.aspx URL. The Search Results page from this Home Page uses different HTML (though it looks the same) compared to the search results pages of normal /Home.aspx or similar pages. Search related code was refactored in its entirety to be more resiliant to future changes and to include tracking of this Enterprise Search page.


Fix: Correct Modern Document Library Preview window related behavior

Update code to correct issues tracking the Document Library Preview windows Command Bar including the Download and Previous/Next buttons (Issue 1124, 1125, 1128)

Changes in SharePoint Online modern view Document Library Preview windows (open an image) resulted in lack of proper tracking of clicks to the various Command Bar links. This update corrects the tracking for these links and improves tracking for some in cases of a page refresh or similar event.


Enhancement: Add Link Tracking support for Modern alterative Web Part Layouts

Update code to support alternative layouts of the News and Hero web parts (Issues 659, 1078)

SharePoint Online modern view offers web parts that provide alternative layout options to be customized for the page. Previous iterations of the code supported only the default layouts, and changing to alternative layouts altered the behariof of the tracking. This primarily results in lack of tracking of clicks to News and Hero web parts in other layouts as these use custom code to track their specific interactions. This update adds support for the other layouts of the Hero and News web parts. Other web parts with layout options are not reliant on custom code and generally tracked with the default link tracking code.


Fix: Correct inaccurate URL data on clicks to links with a Query String but no URI stem

Update code to correct interpretation of URL components on links that have a query string but no URI stem (Issue 1150)

Clicks to links that have a Query String (e.g. ?query=example) but no URI Stem (e.g. /teams/sitecollection) such as https://example.sharepoint.com?query=example were being misinterpretted by the code and resulting in the URL being broken up into pieces incorrectly for reporting (each component is sent using its own parameter e.g. dcsuri=/teams/sitecollection). This update corrects interpretation of URLs when no URI Stem if found.


Was this article helpful?