Anjular.js fragment identifier “#” hash issue with SharePoint 2019 Modern UI

20/11/2019

OnPrem SharePoint 2019, Modern UI, Horizontal Navigation Bar trimming special characters in our case “#” (Hash) in query strings for link entries which breaks 3rd Party Angular.js navigation.
like: http://www.contoso.com/home.aspx/?#/banner/yellow

(Btw:This issue is not present on SharePoint Online)

This issue only happens with SharePoint 2019 Modern UI and if you store your links with Vertical or Horizontal Navigation OOB control.

The reason is OOB Modern UI Navigation components trims any fancy character including hashes (#) where it is required for your angular.js custom solution navigation or routing purpose.

For resolution; you may try following workarounds:

There are several articles in related Angular design and how it may change this behavior.

There are always some issues we are expecting integrating 3rd party tools with SharePoint. We are trying to support as much as possible 3rd party JS library usage with SharePoint like Angular.js, but we don’t have support for Angular.js itself. It is an open source project that we cannot help much to removing “#” on Angular.js for angular navigation. This is out of scope for Microsft Support.

Luckily, Microsoft SharePoint product group fixed that behaviour and the resolution has been addressed with November CU 2019 for SharePoint Server 2019.

November 2019 CU for SharePoint Server 2019 is available for download

 

 

Advertisement

Filed under SharePoint 2019 Tagged with , , , , , , ,

Problem about using Metadata navigation with column filters together.

12/12/2014 Leave a comment

Hello,

Recently we have facing incidents for SharePoint 2013 and SharePoint Online about using “Metadata Navigation Filtering” with “Column Filters” together problem.
You can find more information how to setup “Metadata Navigation Filtering” for a list in details.
https://support.office.com/en-us/article/Set-up-metadata-navigation-for-a-list-or-library-c222a75d-8b18-44e2-9ed8-7ee4e0d23cfc?ui=en-US&rs=en-US&ad=US#_Toc325632511

Well in our scenario; i have created a “departments” column as “Metadata Column” ( Which is using a term set behind )
Then configure the list -> List Settings->Metadata Navigation Settings and add “Departments” column to “Selected Hierarchy Fields” section.

Our default view looks like that.

 

Metadata1

We have selecting some record in “Metadata Navigation Panel” from left side of the page for filter by Metadata Navigation feature

metadata2 metadata3

And Selecting “ID” column to use “Column Filter” by selecting an item like “2” in example

Metadata4

And facing the problem it is not filtered correctly . Just order changed.

metadata5

https://support.office.com/en-us/article/Set-up-metadata-navigation-for-a-list-or-library-c222a75d-8b18-44e2-9ed8-7ee4e0d23cfc?ui=en-US&rs=en-US&ad=US#_Toc325632511
We say “Metadata navigation works together with other filters for the list, such as views and column filters.”
But this is currently not supported (12/12/2013 SPS2013 Build:4675) in Client Side Rendering (CSR). By default the views render with client side rendering.
You can get more details about CSR if you are not familiar with it by below article.
http://msdn.microsoft.com/en-us/library/office/jj220045(v=office.15).aspx

The solution is very easy if you want to use them together ;
Edit the default page of the Document Library  ,
Edit Web Part – (the list view webpart)
Under “Miscellaneous” section mark the list view webpart as “Server Render”

metadata6MetaData 7

After you save the page (stop editing) again and test above filtering again;
You will see the Metadata navigation with column filters is working correctly :

Managed8

Currently the webpart are rendered by Server and the problem is not happen.

 

 

Filed under SharePoint 2013, SharePoint Online Tagged with , , , , , ,

Multiple Navigation Nodes Problem and Navigation Deadlock in SharePoint 2010

12/02/2013 Leave a comment

Symtoms:
Issue happens after  August 2012 CU installed for SharePoint Server 2010.

After publishing a new page the site load times start to increase dramatically or page requests don’t finish loading at all. You will see the infamous “An expected error has occurred“-error or if the callstack is enabled and custom errors are turned off in the web.config (CallStack=”true” / customErrors mode=”Off”) you will see a “Request timed out.” error-message.

System.Data.SqlClient.SqlException: Transaction (Process ID 76) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.HasMoreRows()
at System.Data.SqlClient.SqlDataReader.ReadInternal(Boolean setTimeout)
at Microsoft.SharePoint.SPSqlClient.ExecuteQueryInternal(Boolean retryfordeadlock)
at Microsoft.SharePoint.SPSqlClient.ExecuteQuery(Boolean retryfordeadlock)

PortalSiteMapProvider was unable to fetch children for node at URL: /<site>, message: An unexpected error occurred while manipulating the navigational structure of this Web., stack trace:
at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)
at Microsoft.SharePoint.Library.SPRequest.UpdateNavigationNode(String bstrUrl, Int32 lNodeId, DateTime dateParented, String bstrName, String bstrNodeUrl, Object& pvarProperties, String& pbstrDateModified)
at Microsoft.SharePoint.Navigation.SPNavigationNode.Update()

Resolution:
 SharePoint April 2013 CU

For more details and for workarounds :
http://blogs.msdn.com/b/joerg_sinemus/archive/2013/02/12/february-2013-sharepoint-2010-hotfix.aspx

Filed under Uncategorized Tagged with , , , , , , ,