JSLink not working when using any list ViewStyles other than default.

Question

Hi,
I have a custom field and i am doing client side rendering of it using JSLink for ListView form. I started by applying the JSLink in custom field class.
public override string JSLink
get { return myJSLinkPath; }
set { base.JSLink = value; }
Everything seems to work fine and i can see my custom field get rendered properly. Till this point i was using the default sharepoint list view style. After sometime i decided to use the shaded listview style which is <ViewStyle ID="17"
/> to get the alternating row color style in my list. After applying this style, my JSLink stopped working, infact it is not even registered on page now. I have tried different ways to set JSLink property like it is mentioned in the following link but it
didnt worked.
http://www.martinhatch.com/2013/08/jslink-and-display-templates-part-1.html
So my question is, how to apply JSLink while using the shaded (or any other) viewstyle?

Answer 1

Arham,
When you register your display template, I'm guessing you're using both ListTemplateID and BaseViewID in the registration code?
It's likely that the BaseViewID is different for the Shaded ViewStyle. You should still see your code registered on the page in the Head element, but when it runs I think the registration is getting ignored.
Using the debugger in IE or chrome should allow you to step through the Display Template registration and double check what the value of BaseViewID should be.
You can of course override this if you want, I use a similar method in a blog post on fixing the clash with multiple web parts and JSLink on a page which may help you.
http://www.myfatblog.co.uk/index.php/2013/09/listview-web-part-issues-with-jslink-and-display-templates-a-solution/
I'll give this a test on my dev environment when I get home and see if I get the same results when adding the JSLink through the webpart properties.
##EDIT##
Ok, I tried this at home using a Field Display Template and it worked on all the different styles, however this was with the JSLink deployed through the list view web part properties, not declaratively in the field declaration.
It does prove however that it's not the BaseViewID causing the problem.
##/EDIT##
Paul.
Please ensure that you mark a question as Answered once you receive a satisfactory response. This helps people in future when searching and helps prevent the same questions being asked multiple times.