Tag Info

Hot answers tagged

3

Package a WSP Right click your project in the right column. Then click "Publish". A dialog will open, where you will get to choose where to place the resulting .wsp file. After clicking "Publish" your project will be build and then packaged in the selected location. Make sure to have the Solution configuration set to Release when building for production. ...


3

Why are you using the client side ID. Use the server side ID "abc". It will work. Regards.


2

I suspect this behavior could be related with JavaScript template itself. It seems that when XLV web part is instantiated via Visual web part, custom template is not applied since clienttemplates.js (part of CSR library) library is not yet loaded. In order to make sure the custom template is registered property, try to enclose it using SP.SOD.executeFunc ...


1

You can save User data as below string[] userarray = a.CommaSeparatedAccounts.ToString().Split(',');; SPFieldUserValueCollection usercollection = new SPFieldUserValueCollection(); for (int i = 0; i < userarray.Length; i++) { SPFieldUserValue usertoadd = ConvertLoginAccount(userarray[i]); usercollection.Add(usertoadd); } ...


1

I was able to get my solution upgraded from a 2010 project to 2013 using the following. Note that this will update your solution to use the new 2013 API. It is possible to update just the project file but still run in 2010 mode. First edit your .csproj file (for c#). Modify the target framework to this: ...


1

Not sure but this could be the problem: lvwp.JSLink = "~site/_layouts/15/JS/jquery2.1.1.min.js|~site/_layouts/15/JS/JSLinkFields.js"; I think you should remove the ~site part from the URL:s, like this: lvwp.JSLink = "/_layouts/15/JS/jquery2.1.1.min.js|/_layouts/15/JS/JSLinkFields.js"; Also make sure to set the ClientRender ...



Only top voted, non community-wiki answers of a minimum length are eligible