Skip to main content
SharePoint

Return to Answer

improve format , readable
Source Link
edit approved Aug 4, 2016 at 14:07
Mohamed El-Qassas MVP ♦
edit approved Aug 4, 2016 at 14:07
Mohamed El-Qassas MVP ♦
  • 45.4k
  • 9
  • 55
  • 96

It's actually the opposite; I can confirm that custom actions run before jslink. It works out well that this is true. If you have the same dependency in inon a number of jslink scripts, you can load it once as a site or web custom action. The

The alternative is to set all of your jslink to "~sitecollection//jquery.js|~sitecollection//yourscript.js" "~sitecollection/<path>/jquery.js|~sitecollection/<path>/yourscript.js" which gets pretty messy as dependencies grow.

It's actually the opposite; I can confirm that custom actions run before jslink. It works out well that this is true. If you have the same dependency in in a number of jslink scripts, you can load it once as a site or web custom action. The alternative is to set all of your jslink to "~sitecollection//jquery.js|~sitecollection//yourscript.js" which gets pretty messy as dependencies grow.

It's actually the opposite; I can confirm that custom actions run before jslink. It works out well that this is true. If you have the same dependency on a number of jslink scripts, you can load it once as a site or web custom action.

The alternative is to set all of your jslink to "~sitecollection/<path>/jquery.js|~sitecollection/<path>/yourscript.js" which gets pretty messy as dependencies grow.

Source Link
Joe McShea
Joe McShea
  • 1.5k
  • 9
  • 15

It's actually the opposite; I can confirm that custom actions run before jslink. It works out well that this is true. If you have the same dependency in in a number of jslink scripts, you can load it once as a site or web custom action. The alternative is to set all of your jslink to "~sitecollection//jquery.js|~sitecollection//yourscript.js" which gets pretty messy as dependencies grow.