Hot answers tagged

6

PROBLEM SOLVED :-) :-) The bug of trying to set the xsllink property through the template seems to be a recognised bug. I'm even sure MS are aware of this as when looking at how they have created their site definitions it seems pretty uninstinctive. The Solution DO NOT SET OR DEFINE THE XSLTLISTVIEWWEBPART IN THE TEMPLATE instead just define a webpart ...


5

BaseViewID 0 is intended for using in views, which are added to home page! Remember, when you're adding a XsltListViewWebPart to a page, you can select to display "Summary view" in webpart properties. This is actually "BaseViewID=0" view. Source: How can I use normal paging on a custom view?


5

I ran into the same issue recently and found that you need to use '&#xD;&#xA;' (HTML-encoded carriage return + line feed) for newlines in the description field. This will result in SharePoint rendering a <br> tag in the browser.


4

After analyse the trace logs, I found the solution (for my case). The content of attribute Path is relative to the installation path of the feature, e.g. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\FEATURES\myproject\MyListInstanceName\ The content of attribute Path is relative to the template path, e.g. C:\...


4

I'll assume what you are trying to do is change a Choice field's type using PowerShell. In that case you can do something like this: $web = Get-SPWeb -Identity http://your.site.url.here $list = $web.Lists["YourList"] $field = $list.Fields["YourField"] $field.Type = [Microsoft.SharePoint.SPFieldType]::MultiChoice $field.Update() The SharePoint SPFieldType ...


3

Your patch levels are different. Install May 2015 CU or MS15-046 to the production server, depending on what was installed in dev/test.


3

You can not use people picker column type as a lookup field. Refer this link for reference, http://techtrainingnotes.blogspot.in/2012/01/sharepoint-not-all-column-types-can-be.html People Picker Lookup Column As we are working in SharePoint, we have to play within its boundaries...;) Hope this will help you.


3

Writing queries directly on SharePoint databases is highly discouraged. You should consider the database as a black box which you can interact with through the provided APIs (either SSOM, CSOM, REST or web services). Here's how you can retrieve a view definition, using SSOM: SPView oView = oWebsite.GetViewFromUrl("Lists/List_Name/View_Name.aspx"); var ...


3

Also you should have preview file for your custom theme. For example: mymaster.html mymaster.master mymaster.preview


3

It seems that you are using wrong identifiers for the three fields Title, LinkTitle and LinkTitleNoMenu. The correct ones should be: Title --- fa564e0f-0c70-4ab9-b863-0177e6ddd247 LinkTitleNoMenu --- bc91a437-52e7-49e1-8c4e-4698904b2b6d LinkTitle --- 82642ec8-ef9b-478f-acf9-31f7d45fbc31 I have tried to search for the guid you are ...


2

have you tried using 15 hive in path? <Form Type='NewForm' Url='NewForm.aspx' Path='_layouts\15\myproject\myUI.aspx' WebPartZoneID='Main' />


2

<Query> <Where> <Or> <And>...</And> <IsNull> <FieldRef Name="StartDate" /> </IsNull> </Or> </Where> </Query>


2

Double check the location of themeurl, fontschemeurl!!! It must be placed under /_catalogs/theme/15 <Field Name="ThemeUrl">~sitecolletion/_catalogs/theme/15 .... </field> <Field Name="FontSchemeUrl">~sitecolletion/_catalogs/theme/15 .... </field>


2

An ampersand in XML must be escaped as &amp;, so your software is behaving quite correctly. When the XML is parsed by the recipient, assuming a correct XML parser, it will translate the escaped &amp; back to &.


2

Sequences and actions are events that occur when you upgrade Microsoft SharePoint Products and Technologies. The upgrade process consists primarily of sequences and actions. A sequence may be repeated if there are multiple items of the same type. For example, a sequence may be repeated if there are multiple content databases, multiple Web Applications, or ...


2

A CAML query for that would look something like this <View> <Query> <Where> <Contains> <FieldRef Name='Title'/> <Value Type='Text'>username</Value> </Contains> </Where> </Query> </View> But I do wonder why you ...


1

The problem was caused by UserId being null in several elements of the data received from the HTTP Get, while that is set as required in the JSON Schema... initially we solved it by using the below in the HTTP Get: _api/web/sitegroups/getbyname('Legal Owners')/users?$filter=UserId+ne+null Then we were given a better and more elegant solution on the Power ...


1

Try removing UserId from the 'required' array at the end of your JSON schema. Any values specified in that array must be present with every return/trigger, or the Flow will fail. If 'Email' is the only value you truly need, I would make that the only required value. Like this: "required": [ "Email" ]


1

Here is the method that I use. It uses AJAX and ODATA. It will give you the properties of both the fields and the views. You would just iterate over them afterwards. I can include more details latter. var myFilter = 'lists/GetByTitle(\'Site Assets\')?$select=Fields,Views&$expand=Fields,Views', jax = $.ajax(get_SPFolderBaseData('webAbsoluteUrl', ...


1

You can try two method. Use "Save as Template" feature to save that list as template( unchecked the include content). Then download the template, and move to 2nd farm. Now upload the Template to the site collection and activate it, Lastly create the List using that template. also look this http://blogs.interfacett.com/sharepoint-2010-saving-a-custom-list-as-...


1

You need to apply Service Pack 1 on the production environment that is running the RTM version. No patches are needed before applying SP1. Download the correct type (Foundation, server or project server) for your farm and apply the service pack to all the servers in the farm, and then run the configuration wizard on each one of the servers. So if you have ...


1

You will be out of support of Microsoft. I dont think we can predict what will goes wrong as its depend what you change/ add/delete? Microsoft cannot reliably predict the effect to the operation of these products when parties other than the Microsoft SharePoint Development Team or Microsoft SharePoint Support agents make changes to the database schema, ...


1

You probably didn't add these properties to <List> in Schema.xml: ThumbnailSize="160" WebImageWidth="640" WebImageHeight="480" And these fields to View: <FieldRef Name="DocIcon" /> <FieldRef Name="PreviewOnForm" Explicit="TRUE" /> Without them the thumbnails aren't shown.


1

CAML is case sensitive. The problem is that in your Custom Action declaration, the RegistrationID is "0X0100..." and it should be "0x0100...". Cheers!


1

You can only use checkboxes in a Choice field, but since you need to use values from another list you need to use a Lookup column which doesn't support checkboxes. The lookup field allows multiple values though. Because none of the above actually match your business requirement, you'll have to develop a custom field which can inherit from the lookup field. ...


1

I used following steps to create custom survey list: Create ListInstance. Elements.xml: <?xml version="1.0" encoding="utf-8"?> <Elements xmlns="http://schemas.microsoft.com/sharepoint/"> <ListInstance Title="CustomSurvey3" OnQuickLaunch="TRUE" TemplateType="102" Url="Lists/CustomSurvey3" ...


1

If you use custom schema attribute, you can't declare one more view. You can remove an existing one and create your own, using the BaseViewID of the one you removed.


1

changes apply on any other fields except this Primary key !!! field because it is a reference. But before create this list, it is possible by change with new content type that you should create new one in your site application then correct GUID's for Title --- fa564e0f-0c70-4ab9-b863-0177e6ddd247 LinkTitle --- bc91a437-52e7-49e1-8c4e-4698904b2b6d ...


1

I think I have had this problem before and just doing an IISRESET, [Edit]Recycle of SP User Code Host Service[End edit] and restarting Visual Studio before the redeployment solved the issue for me. I may be completely wrong but it seems Visual Studio maintains some kind of cache which holds the old schema.If I did not restart visual studio, I would get the ...


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