Tag Info

New answers tagged


Like to note that RootFolder as you point out yourself is not a bad idea if you were to use REST (and not jsom), like this: /_api/Web/Lists?$filter=RootFolder/Name eq 'MyImages' Then just pick the first one, and you get one result with all additional list data. (Syntax tested on 365, might need $expand on-premise.)


How to get List by its Url: function getListByName(name,success,error) { var ctx = SP.ClientContext.get_current(); var lists = ctx.get_web().get_lists(); var result = ctx.loadQuery(lists, 'Include(RootFolder)'); ctx.executeQueryAsync( function () { var list; for(var i = 0; i < result.length; i++) { ...


This is my code for vwp properties: private string _lista = ""; [WebBrowsable(true), WebDisplayName("[some name]"), WebDescription("[some name]"), Personalizable(PersonalizationScope.Shared), Category("some category")] public string _Lista { get { return _lista.ToString(); } set { _lista = value; } } As you can see the only diference with your ...


You are trying to read the property values too early in the web part life cycle. The property values are populated from the content database after the constructor has run. If you check the property values in OnLoad or OnPreRender you will see the values you have set in the editor.


The solution to this was a lot simpler than I expected: I activated content types for the site and set the Document Status column to 'Hidden' rather than 'Optional', and now the column can't be seen from the Excel. Just thought I'd answer my own post for anyone who finds themselves in a similar situation and comes across this.


If you don't want to use the GUID, you'll have to make an extra call and get the vti_listname property from the list folder. The folder you can get by url using the getFolderByServerRelativeUrl on the SP.Web object. Example: var clientContext = SP.ClientContext.get_current(); var web = clientContext.get_web(); var folder = ...

Top 50 recent answers are included