Hot answers tagged

4

Set Always Force Install to True in for your feature. (Assuming you are using Visual Studio)...Check the feature property window and you should see this option! If you are using PowerShell, you can also use : $sln = Add-SPSolution mySolution.wsp Install-SPSolution -Identity mySolution.wsp -GACDeployment -Force


3

By default, all sites, lists, and libraries in a site collection inherit permissions settings from whatever is directly above them in the site hierarchy. This means a site inherits permissions from the root site of the site collection, and a sub site inherits permissions from its parent site. A list inherits permissions from the site that contains the list. ...


3

Stop using PATH and use Content Types. It makes requirements like this a breeze. Create a new content type based on Document. Assign the content type to the library. Optionally remove the Document content type Assign the documents in the library to your content type Crawl the content Find the content with a result source ContentType=MyContentType


3

At least I typed my own text LOL In the Filter settings of a View you can only use [Today] as is, you can do simple +- calculations but you can not use Functions. So you need to add two Calculated Columns calculating january1st =DATE(Year([YourDate),1,1) and december31st =DATE(Year([YourDate),12,13) and then compare in your View Filter if [Today] ...


3

This works for me: =[Today]+14 And this is end result:


2

You can use Search query Webpart for this and use filters to refine your result set. Have a look at the following link on how to configure this Using-content-search-web-part-and understanding SP2013 search


2

The SharePoint Active Directory Import does not mark the profile to be deleted either with incremental or Full Import when they are not selected and only way to remove the obsolete users is here. You can follow below mentioned steps to solve your issue. Run Full Import Post that run Use SharePoint Management Shell to Run following Management Shell ...


2

Actually, there's no such thing as "deploying a Web part to a site collection". You deploy a Web part with a WSP package; WSP packages (at least ones that contain Web parts) are deployed against specific Web applications. After that the feature containing the Web part is activated per site collection, but "activating a feature" is only a SharePoint logic ...


2

After Googling 'body' rather than 'payload' (as per my original question title) I found this blog post linked from a MSDN thread. It says that you need to select Advanced Properties from the ribbon, and set the RequestHeaders and RequestContent options explicitly.


2

Not sure what you are trying to do. However, you can use: Calendar Header ms-acal-header Calendar Body ms-acal-rootdiv


2

You can go with the following ID also AsynchronousViewDefault_CalendarView This is the ID of the Parent div of div having following class ms-acal-header


2

That is part of the Enterprise edition of SharePoint Server. This functionality will not be available to you with SharePoint Foundation. Office Web Apps is not a factor here.


2

First, put all the styles in a css file and upload it to the Site Assets library, then you can reference it in couple of ways to do this: Option 1: Site Settings ==> Under Look and Feel ==> Master Page ==> Alternate CSS URL and enter the URL to your custom css file, like this /SiteAssets/CSS/styles.css Option 2: Edit your master page (always make a ...


2

It is a site collection level feature so you can not do it on site-level. Site Collection Upgrade: One the benefits of upgrading to SharePoint 2013 is that it all happens behind the scenes. This means that your site collection administrators can upgrade the look and feel – not to mention, handle the change management – on their own ...


2

What about this to add 4 , 2 or 0 days =[Project Start Date] + [Delivery Days] + IF( [Delivery Days] > 9 , 4 , IF( [Delivery Days] > 5 , 2 , 0 ) ) And if you want to calculate "For Every Week Add 2 days" look into the MOD function ...


2

You can use the following code using(SPSite oSite = new SPSite("site url")) { using(SPWeb oWebsite = oSite.OpenWeb()) { SPList oList = oWebsite.Lists["Tasks"]; SPListItem oListItem = oList.Items[5]; oListItem["Title"] = "Some Title"; oListItem.Update();// without this line item will not update } } Read more ...


2

I do not see any harm on using Visual Web part. Its easy and you have the full control on it. Having a custom list in the back end with appropriate fields will empower your users to easily add and edit the menu items. Since its a visual web part, you have a flat canvas on which you can paint any type of tile design. Also writing server object model code is ...


2

No, you can't force browsers to support features that aren't available. Browser compatibility is a lot better than it was, there are still things that are reliant on ActiveX controls. See the Plan browser support in SharePoint 2013 TechNet article. https://technet.microsoft.com/en-us/library/cc263526.aspx


2

You would want to use [Today]+14 for this.


2

It can be solved by disabling loopback check. Refer this link: http://www.c-sharpcorner.com/UploadFile/shyjumohan/disable-loop-back-check-in-windows-server-2012/ FYI, Microsoft has introduced a security feature in 2003 Server to prevent attacks on Windows servers. This feature will prevent a web application access from the host server with a fully ...


2

If you migrate content only with the tool, yes you might bypass the warning messages you get when doing a database attach migration. You may still encounter problems depending on what these customizations did. In our experience with using a third party tool to go from 2010 to SPO, all of the customizations we knew of were not carried over (obviously) and ...


2

Yes, it can be done in the Content Editor Webpart check this step by step tutorial http://www.queness.com/post/5368/quick-and-easy-jquery-read-more-script-tutorial


2

You can jump straight from SP1 to the April 2016 CU. You do not need to install any previous patch besides the minimum the CU requires. In the case of April 2016, that would be SP1. When installing any SharePoint 2013/2016 patch, I would recommend using this script to do so. It will speed the binary installation up to about 20 - 30 minutes from ~3 - 5 ...


2

Cumulative Updates include all previous updates. From http://sureshpydi.blogspot.in/2013/11/difference-between-cumulative-updates.html?m=1 Cumulative update is collection of all the hot-fixes up to date. Generally Office hot fixes are released for every two months in a package. It includes fixes for all the issues collected from hot-fix accepted ...


2

You can achieve this functionality using Alert Me. following are the steps. 1: Go To your Calendar 2: Go To "Alert Me"(on Ribbon) --> Set alert on this list 3: Configure your alert. 4: Done


2

You can try this script $web=Get-SpWeb "http://subsiteurl" $web.AllowUnsafeUpdates=$true $web.ServerRelativeUrl="/newRelativeURL/" $web.Update() $web.AllowUnsafeUpdates=$false


1

When you create a workflow, you can choose when the WF should start. So what you need to do is to adjust the current workflow to only kick in when the item is created and create another WF to run when the item is modified (with a different email body).


1

You can check if condition for the approval block with the workflow status hidden field. Create on hidden column called IsApproved & give default value as No At the time of new item creation inside the approval block, Update the IsApproved field as Yes In the workflow check if IsApproved equal to false then go to approval Please refer the below image ...


1

We are using the same way, we have DNS entry which points to SQL server. We prefer the DNS entry upon SQL alias. For DNS entry, in case of failover down timer is higher then sql alias. You can go either SQL Alias or DNS entry. You can read the below blog for nice comparison: https://junfengzhang.com/2014/08/16/dns-alias-vs-sql-server-alias/


1

First, you want to make sure that you published the WF and you can verify that you have the latest version (check WF version history). The other workaround is to create a column (single line of text and call it NewWF and default value is Yes), then check the option to start the wf on start. the first step of your workflow will be check the value of that ...



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