SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a custom field type with a fldtypes_xxx.xsl template that we have carried forward from a 2010 solution into a 2013 solution. The Number_body template we are using works just fine. However, I cannot get the header template to work.

For the FieldRef I have tried matching the ID, FieldType, Type, Name, StaticName, etc. Nothing seems to be able to get it to use the header template.

Any ideas?


share|improve this question
Considering the new CSR technique, which from experience i found quite easy to implement, would it be something you could consider? – Marius Constantinescu - MVP Feb 14 '13 at 15:13
So, in this context we are trying to make it so our current 2010 instances of these fields can be upgraded successfully when migrating to 2013. – John Chapman Feb 14 '13 at 17:35
up vote 0 down vote accepted

From all of my testing, it appears that the current version of SharePoint 2013 does not process the header XSLT templates for custom fields. It is possible this will change in a future update to 2013, but I doubt it.

So, the answer to my own question is that I have to use a different method for accomplishing what I needed to accomplish in the header template. In this case, it was adding JavaScript for the rendering of the fields. So, rather than use the XSLT template for this, I added code in an AdditionalPageHead delegate control that is part of the same feature that adds the custom field. In this control, it checks to see if the SPContext.Current.List.Fields collection contains the field and then add the scripts to the page.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.