Tag Info

Hot answers tagged

2

I would suggest that you break the whole thing into two features, first one to deploy the List Template and second one to create the instance of the list based on template.. On the later one, you will need to define Feature Activation Dependency of List Template feature.. Both features can be hidden and you just need to activate the Feature that creates ...


2

About the first one: since it is a note field, I suppose that that is the actual content of the field. SharePoint automagically formatted your text when you inserted it into the list. About the second one. Again, expected. The user will be returned as an instance of the FieldUserValue class. Cast it to read the actual info. For example: //Note: will give ...


1

Yes you must use content type for this case! Go to Site Setting and site content type then Create 2 content type for each them and create them columns! So create a list and go to list setting and Advance setting so Choice Allow management of content types? Yes. Add from existing site content types then add your content type. Then Go to form setting and then ...


1

There is a FieldMultiLineText class in CSOM which is equivalent to SPFieldMultiLineText class of Server object model.You can try the below code : dish.FieldValuesAsText["Ingredients"]; Also you have to include the FieldValuesAsText property in the load statement like below: context.Load(dishes,items=>items.Include(item=>item.FieldValuesAsText));


1

Not quite sure what you mean, but I'm guessing you have at least one item in your list with the values you explain, set to a field of type Text. If this is the case you can convert the field to MultiChoice through PowerShell, like this: $field = $list.Fields.GetFieldByInternalName("MyField") $field.Type = "MultiChoice" $field.Update() You also have to add ...


1

Are you changing the list columns/content types within deployments? If not, then you could change your solution so that it only deploys list definitions and then write a feature receiver to instantiate the list from the definition. In a similar situation, I used code like the below (SP2013 but should work in 2010) if (oWeb.Lists.TryGetList("ListName") == ...


1

For the user you need to get the LookupValue property and then use toString(). objFieldUserValue.LookupValue.ToString(); Microsoft.SharePoint.Client.FieldUserValue Title For the NoteField try to get the property Text. NoteField properties


1

Found the solution. All it took was replacing this bit of code: var h3 = '<h3>' + oListItem.get_item('Title') + '</h3>'; var div = '<div>' + oListItem.get_item('Floor') + '</div>'; var content = $(h3 + div); content.appendTo("#accordion").show(); with this bit of code var newDiv = "<h3> " ...


1

A cleaner way would be to create a new View with all necessary filters and use it on the pages(as Webpart) and apply JSLink to the web part properties. JSLink: You could always add a conditional check within the JS but that might offset the paging and result in empty cells. For ex. customItemHtml: function (ctx) { var _taskStatus = ...



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