Problem about using Metadata navigation with column filters together.

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.

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

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

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

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”

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 :

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