Alert on view in document library triggers unwanted alerts

A user has configured an alert on a document library view.
She still receives alerts from documents that do not belong to the specific view in this document library.
This is the only alert she has configured.
The alert seems the be correctly created.
Any ideas? Thanks, Johan
Johan Celis

Hi,
Based on your description, my understanding is that the user created an Alert on views in a document library, but she still received alerts from documents that do not belong to the specific view in this document library.
For your issue, first, make sure that there aren’t any other alerts on the documents.
Second, we can set up alerts on views in a document library
with the following things to be considered:
1. When you create an alert under Send Alerts for these changes section an option
"Someone changes an item that appears in the following view" appears with a drop down of all your views (so you can select any view you want to create alert from the DD choices)
2. This option is only available when you create views by filtering a column.
Best Regards,
Lisa Chen
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]

Similar Messages

View of Document Library showing only documents based on dates in columns.

I have a document library which includes only one content type of "Job Posting", which includes a "Posting Date" column, and a "Closing Date" column. I want a Web Part View of this library that will only show the documents when
the current date is after the Posting Date and before the Closing Date. What is the best approach?

Hi,
I usually create a view with filter OOTB and then change the query inside SharePoint designer, may be you can try this approach. here is a Q&A on this topic in this forum -
http://sharepoint.stackexchange.com/questions/26364/filtering-a-list-with-date-ranges-xslt-advanced-expressions-on-list-filters
Hope this helps!
Ram - SharePoint Architect
Blog - SharePointDeveloper.in
Please vote or mark your question answered, if the reply helps you

View Workspace Document Library on a PDP -- Project Server 2013

Regards!!
In Project Server 2010 exists a Solution Starter called "Project Workspace List Viewer". I need the same solution but in Project Server 2013, is this possible?? does somebody has created the same solution??
Thanks for your help!!

As per the link mentined below it wont work for 2013.
http://social.technet.microsoft.com/Forums/projectserver/en-US/bbedf949-acdc-4c75-83fc-e59f84fe77bc/displaying-the-contents-from-project-site-to-project-web-app?forum=projectonline
kirtesh

Sharepoint 2013 Document library view show version history

Hello everyone,
I have a document library view with many folders. Each folder is a procedure and have document attached to it.
When I add a new version, I would like to show version history for each document contained in the folder. For example:
There is a folder Procedure 123 which has three files ( File1, File2, and File3). After a week the user the user created new revisions for each document.
I would like to have a document view with the following information
File Name   version
====== ======
File 01         0
File 02         0
File 03         0
File 01         1
File 02         1
File 03         1
File 01         2
File 02         2
File 03         2
Thanks for your help.
Jhonny Marcelo

This is quite simple, you have to modify the current view (Modify this view) of document library and then you can select version column from available column list (make sure version is enabled). please check below picture for detail.
Adnan Amin MCT, SharePoint Architect | If you find this post useful kindly please mark it as an answer.

Create document library with 2 columns multitext and lookup.

Remove-PSSnapin Microsoft.SharePoint.PowerShell -erroraction SilentlyContinue
Add-PSSnapin Microsoft.SharePoint.PowerShell -erroraction SilentlyContinue
#To which site u want to create the list
$spWeb=Get-SPWeb -Identity http://xyz
#List type or template
$spTemplate = [Microsoft.SharePoint.SPListTemplateType]::DocumentLibrary
#Get all the lists to the listcollection
$spListCollection=$spWeb.Lists
#adding the new list to the list collection
$spListCollection.Add("Student1","Student1",$spTemplate)
#get the path of subsite and sitecollecion
$path = $spWeb.url.trim()
#get the list to the list object
$spList = $spWeb.Lists["Student1"]
#adding the field type(Note) to the list
$spFieldType = [Microsoft.SharePoint.SPFieldType]::Note
$spList.Fields.Add("COMMENTS",$spFieldType,$false)
$ParentList = $spWeb.Lists.item("Studentlist")
$spList = $spWeb.Lists["Student1"]
$spList.Fields.AddLookup("lookupcol",$ParentList.id,$true)
$spChildListLookupField = $spList.Fields["lookupcol"]
$spChildListLookupField.LookupField = $ParentList.Fields["ID"]
$spChildListLookupField.Indexed = $true
$spChildListLookupField.RelationshipDeleteBehavior = [Microsoft.SharePoint.SPRelationshipDeleteBehavior]::Restrict
$spChildListLookupField.Update()
$Views = $spList.Views["All Items"]
$Views.ViewFields.Add("COMMENTS")
$Views.ViewFields.Add("lookupcol")
$Views.Update()
$spWeb.Dispose()
I am trying to create a document library with 2 coulmn types multitext and look up but i am getting the following error
I am getting erros - You cannot call a method on a null-valued expression - $spList.Fields.Add("COMMENTS",$spFieldType,$false)
Cannot index into a null array.
+ $spChildListLookupField = $spList.Fields["lookupcol"]

Hi,
I used the PowerShell you offered to do a test in my SharePoint 2013 and I reproduced your issue. I solved it by doing a little change to the PowerShell which you offered.
Because you create a document library, the default view of document library is "All Documents" rather than "All Items", just change
$Views = $spList.Views["All Items"]
to
$Views = $spList.Views["All Documents"]
Best Regards,
Lisa Chen
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Displaying Document Name With The Summary in a Single Column Using Document Library View.

Hi All,
I have a question that relates to SharePoint Document Library Views. I want to view the Documents name with the summary in a single column. Below image shows an example of it. I need this within a SharePoint Document Library. Also I want the height of the
row to be increased more than the default height. I cannot figure it out how to do that? Could you someone help me to do this. I have inserted the Document Library as an App Part to the page.
So could you someone help me to solve this matter?
Thanks and regards,
Chiranthaka

HI Chiranthaka,
You can create DataView webpart using SPD and then modify the display template according to your need.
http://deannaschneider.wordpress.com/2012/07/10/item-counts-dvwp-sp2010/
Hope this will help to solve your problem.
Best Regards,
Brij K

Displaying Document Name & The Summary in a Single Column Using Document Library View

Hi All,
I have a question that relates to SharePoint Document Library Views. I want to view the Documents name with the summary in a single column. Below image shows an example of it. I need this within a SharePoint Document Library. Also I want the height of the row
to be increased more than the default height. I cannot figure it out how to do that? Could you someone help me to do this. I have inserted the Document Library as an App Part to the page.
So could you someone help me to solve this matter?
Thanks and regards,
Chiranthaka

HI Chiranthaka,
You can create DataView webpart using SPD and then modify the display template according to your need.
http://deannaschneider.wordpress.com/2012/07/10/item-counts-dvwp-sp2010/
Hope this will help to solve your problem.
Best Regards,
Brij K

Adding "Filter Criteria" to the XSLT List View Web Part impact on "Export to Excel" functionality within Document Library

Hi there,
XSLT List View displaying all the list items within the Document Library. In order to implement the Search functionality within Document library out of box "Text Filter" web part is configured as explained below. The solution is similar to
the one suggested at
http://www.wonderlaura.com/Lists/Posts/Post.aspx?ID=77
"Text Filter" Web Part added to the page.
Filter Criteria (i.e., XSLT List View columns) added to the XSLT List View where the filter parameters take the input from the "Text Filter" Web Part .
3. Both Web Parts (XSLT List View and the Text Filter) are connected.
When the search criteria is entered into the "Text Filter" Web Part, it is passed to the relevant Columns of the XSLT List View and the documents (List Items) that match the search criteria are shown within XSLT List View.
Search functionality working as expected.
Query: Selecting the "Export to Excel" icon from the ribbon generates the excel spread sheet with no data except Column Titles from the Document library. In the investigation it is
found that adding the 'Filter Criteria' on XSLT List View is causing this bug. When the Filter Criteria is removed, then "Export to Excel" functionality is working as expected.
But it is mandatory to add "Filter Criteria" to implement the search functionality with in the document library.
Help: Help/input appreciated on the work around to get the "Export to Excel" functionality work when the "Filter Criteria"
exist on the XSLT List View.
Regards,

Once again thanks very much for your help Scott. very much appreciated.
In the investigation it is found that removing the 'Filter Criteria' on XSLT List View makes the "Export to Excel" functionality work. But the 'Filter Criteria' is mandatory to get the 'Document Search' functionality.
I think that due to technical limitations it should be concluded that 'only custom development can make all work, no code solutions using the SharePoint Designer can meet all the requirements.
If you can think of any alternative solution that could help in resolving the current issue or fix the issue without any custom implementation please inform. Otherwise this issue would be marked as resolved with your suggested response.
Regards,

Not able to create sub folder using SharePoint web service in large SharePoint document library (Item count view threshold limit)

We are trying to create folder & subfolder in a SharePoint document library using SharePoint default(dws) web service. Document library has unique permission as well as item level permission. It was working as expected. Once item count crosses
view threshold limit ( 5000) , create folder web method completes with an error and it creates a folder in SharePoint.
Request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:dws="http://schemas.microsoft.com/sharepoint/soap/dws/">
   <soapenv:Header/>
   <soapenv:Body>
      <dws:CreateFolder>
         
         <dws:url>Shared Documents/VenTest02092015v1</dws:url>
      </dws:CreateFolder>
   </soapenv:Body>
</soapenv:Envelope>
Response:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <soap:Body>
      <CreateFolderResponse xmlns="http://schemas.microsoft.com/sharepoint/soap/dws/">
         <CreateFolderResult><Error ID="2">Failed</Error></CreateFolderResult>
      </CreateFolderResponse>
   </soap:Body>
</soap:Envelope>
While trying to create subfolder under the above created folder service throws an exception saying
FolderNotFound.
Though we are able to create subfolder from SharePoint UI successfully.
Request
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:dws="http://schemas.microsoft.com/sharepoint/soap/dws/">
   <soapenv:Header/>
   <soapenv:Body>
      <dws:CreateFolder>
         
         <dws:url>Shared Documents/VenTest02092015v1/REQ-1</dws:url>
      </dws:CreateFolder>
   </soapenv:Body>
</soapenv:Envelope>
Response:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <soap:Body>
      <CreateFolderResponse xmlns="http://schemas.microsoft.com/sharepoint/soap/dws/">
         <CreateFolderResult><Error ID="10">FolderNotFound</Error></CreateFolderResult>
      </CreateFolderResponse>
   </soap:Body>
</soap:Envelope>

Yes, you're probably hitting the 5000 list item threshold (
http://sharepoint.stackexchange.com/questions/105937/overcoming-5000-file-document-library-limits ). I assume you can do it via the UI because you're probably logged in as an admin in which case, out of memory, the threshold is 20.000 items. You can extend
this limit, but you probably shouldn't.
Kind regards,
Margriet Bruggeman
Lois & Clark IT Services
web site: http://www.loisandclark.eu
blog: http://www.sharepointdragons.com

In a document library : group by view and manage metadata filter & Navigation problem

Hi all, I encounter a problem when configuring a document library using a group by view and in combination with the Managed Metadata filtering and
navigation :
- all the documents appear under my group by, even the ones that does not correspond
- In the other hand, the number in brackets shows the correct number of documents that should be shown
See screenshot below.
Did you already encounter that issue ? Is there a workaround ?

Hi,
According to your post, my understanding is that you wanted to use a group by view and combine with the Managed Metadata filtering and navigation in a document library
to show the corresponding documents with the correct numbers in SharePoint 2013.
In my SharePoint 2013, I created a view which was group by two columns and combine with the Metadata Navigation Hierarchies and Key Filters some fields in a document
library. As a result, it showed only items matching the filter values.
So, I recommend that you can follow the steps to implement it in your environment.
Step1: Enable Metadata Navigation and Filtering:
Metadata Navigation and Filtering is a Site Feature that has to be activated for this to work.
And, the Metadata Navigation and Filtering feature is enabled by default on most sites.
If it is not enabled for your site, you can enable it on the Site Features pages for your site.
You must be a Site Owner or a Site Collection Administrator to enable Metadata Navigation and Filtering.
1. Go to “Site Settings” and click “Manage site features” under Site Actions.
2. Find “Metadata Navigation and Filtering” in the Features list and click “Activate”.
Step2:
Configure Metadata Navigation:
You must have a least the Manage Lists permission level to configure metadata navigation for a list or library.
1. Open the document library for which you want to configure metadata navigation.
2. Go to “Library Settings” of the document library and click “Metadata navigation settings” under “General Settings”.
3. In the Configure Navigation Hierarchies section, select the field or fields you want to display in the navigation hierarchy and then click “Add”.
4. By default, Folders are automatically displayed in the navigation hierarchy. If you do not want folders to display, select Folders, and then click Remove.
5. In the Configure Key Filters section, select the fields you want to add as Key Filters, and then click “Add”.
6. In the Configure automatic column indexing for this list, specify whether you want to automatically create indices on this list to increase the performance of the
queries that users will perform when they use the Navigation Hierarchy and Key Filter columns you've specified. It is recommended that you select the option “Automatically manage column indices on this list”.
7. Click “OK”.
Step3: Set a group by two columns by modifying view in the document library:
1. Go to the “LIBRARY” ribbon of the document library and click the “Modify view”.
2. Click the “Group By” and select up to two columns to determine what type of group and subgroup the items in the view will be displayed in.
3. Click “OK”.
Step4:
Go back to the document library, apply Navigation Hierarchies and Key Filters to do a test in your environment.
The result will like as below:
There is an article about how to apply Metadata Navigation Filtering in SharePoint 2013 for your reference.
http://blogs.interfacett.com/how-to-apply-metadata-navigation-filtering-in-sharepoint-2013
Best Regards,
Linda Li
TechNet Community Support

Display a document library view on a subsite

Hi
I have SharePoint 2013 On-Premise and I would like to display a document library from the top level site in a subsite. This subsite will then be saved as a template and used to create other subsites.
For example,
I have a site called Site 1. In Site 1 there is a document library called doclib1. Site1 also has a subsite called subsiteA.
I would like to display a view from doclib1 in subsiteA. SubsiteA will then be used as a template to create subsiteB, subsiteC etc.
I have tried a few things but these have not worked or I am not doing it correctly. Here is what I have tried
Copied doclib1 code from site1 to subsiteA using SPDesigner. I get the error "List does not exist......"
Used a Content Query Webpart. I get the error "Something went wrong"
Used a Data view web part. The complete page was displayed. I only want the view
Although it looks possible, I do not know how to take this forward. All I need is to display generic documents on each subsite that can be modified from one location.
Marc Collins www.QGate.co.uk

Hi,
To get the custom field in the search filter. You need to follow these steps.
Go to the Search schema from the Manage Service Applications -> Search Service Application in Central Administration
Create a Managed property for your field (Category)
Map the crawl property to the Managed property.
Once managed property created, run the full crawl.
Once full crawl executed, you are able to get your filter property in the search filter.
http://blogs.perficient.com/microsoft/2012/07/sp2013-search-quickie-createmap-a-new-managed-property-powershell/
Even though 2010 article, for 2013 steps are same.
http://johnrossjr.wordpress.com/2011/03/18/creating-custom-managed-properties/
Please mark it answered, if your problem resolved or helpful.

Show the last published documents in a view for a document library.

Hello!
At our company we have a document library with many documents. These documents are evolving and are therefore going from major versions to minor versions to major versions again. To be able to get a good overview of the last "official" versions
we would need to have a view that shows the last "Approved" versions of each document (if any approved versions exist). This is basically the same as watching the document library from a user that only own reading access and therefore only sees the
"published" versions.
In our case this view should be used by people that own editing rights as well to the documents.
Is it possible to accomplish this?
I tried to use the tip from the following site: link
The "?IncludeVersions=TRUE"
did not work though.

Hi AndersObserve,
I understand that you have a document library that you have enabled content approval(if not, enable it) and versioning, then
you want to create a view to filter major(approved) documents, then you can filter on the ApprovalStatus field. Try to create a new standard view, filter the view when the ApprovalStatus is equal to Approved, then the view will display the published version
document.
Best Regards.
Kelly Chen
TechNet Community Support

Document Library Custom View "Grouped By" only shows one group

I have created a Document Library Custom View with the "Grouped By" option turned on and grouped by a column called "media type" which has 3 possible choices. For some reason only the first group is displayed. The other
groups show that they have items in them but can't be accessed. I have expanded turned on.
Here are some screenshots:

Hi zaxxon,
Please check if the above first 6 images (e.g. Managing Threating Confrontations - OneDrive for Business Tutorial)are with value "Training" and "tutorial", if yes, there should be something wrong with the grouped list view of Assets library.
Based on icons from your image, you should be using Office365 SharePoint Online, I would recommend you post this issue in our dedicated Office365 SharePoint online forum below, and I think fixing this issue would be involving back-end support engineer from
server side.
http://community.office365.com/en-us/f/156/t/236901.aspx
Office365 SharePoint Online forum
Thanks
Daniel Yang
TechNet Community Support

SharePoint 2013 document library, permissions to upload and view shared document only

SharePoint 2013 document library I want to give access to client where they can upload and view their uploaded document and can see all documents shared with them.
I have managed to show all document shared with them only by deactivating a feature but now they can't upload any document, If I create a permission set to allow them to upload documents, they will see all other documents as well which are not shared with them.
Any suggestions?

Hi Sharaqat, the best way to handle your situation is to have a separate library or site for the client. You could use item level permissions per Thilosh, but fine-grained permissions become a major headache. You could also use web parts and audience
targeting, but that's not truly secure.
cameron rautmann
I am thinking to have a separate document library for client, where they can upload/view/edit etc, we will upload documents in a "secure" library with a column saying this is a private document or public document, if we mark a document public,
a workflow will move that document to the client's document library. I don't think there would be a problem to move a document from 1 library to another in a workflow.
That's the easiest solution I have found so far.

Different View for same document library on a Wiki Page

Hi,
I am developing a Provided hosted app which have a functionality to create a document library with two Views. Also we need to show this document library in a wiki page with two different views.
I am using CSOM (C#). I am able to create the document library and the two views programmatically. But when I add the document library in the wiki page the default view (All Documents) is shown for both the web parts. There is an hidden view created with
the WebPartDefinition from the xml provided through code.
Through CSOM we are able make a View as default with the link below.
http://sharepoint.stackexchange.com/questions/90433/add-document-library-xsltlistviewwebpart-using-csom-or-web-services
In my case both the webparts will get the same view, where I need different view for same document library in a wiki page.
Also I tried to update the web parts with the following code.
string viewString = @"<View Name='{0}' MobileView='TRUE' Type='HTML' Url='/SitePages/Home.aspx' Level='1' BaseViewID='1' ContentTypeID='0x' ImageUrl='/_layouts/15/images/dlicon.png?rev=23' >
<Query><Where><Eq><FieldRef Name='KeyDocument'/><Value Type='Boolean'>1</Value></Eq></Where></Query>
<ViewFields><FieldRef Name='FileLeafRef'/><FieldRef Name='DocumentOwner'/><FieldRef Name='Modified'/>
<FieldRef Name='_UIVersionString'/><FieldRef Name='Editor'/></ViewFields>
<RowLimit Paged='TRUE'>30</RowLimit><JSLink>clienttemplates.js</JSLink><XslLink Default='TRUE'>main.xsl</XslLink>
<Toolbar Type='Standard'/></View>";
WebPartDefinition wpd = wpfound.FirstOrDefault();
string formattedstring = String.Format(viewString, wpd.Id);
wpd.WebPart.Properties["XmlDefinition"] = formattedstring;
wpd.SaveWebPartChanges();
web.Context.ExecuteQuery();
I created two views (viewString) as shown above.
The above code did not throw error, but it did not update the web part.
Please advise how to move forward.

Hi Samir,
When we click outside of the list view webpart on a webpart page (or allitems.aspx page) with containing multiple webparts, the list view webpart will lose the focus, and the selected items will be deselected, this is by design.
You can look at the following article with using the approach/workaround of Javascript to prevent the specified list view webpart from losing focus.
http://sharepoint.stackexchange.com/questions/44360/list-view-loses-focus-when-additional-webpart-added-to-page
//Set focus on our list web part
var webPart = document.getElementById('WebPartWPQ1');
WpClick({target: webPart});
//Prevent it from losing focus
SP.Ribbon.WebPartComponent.$3_1.deselectWebPartAndZone = function() { };
Thanks
Daniel Yang
TechNet Community Support

Alert on view in document library triggers unwanted alerts

Similar Messages

Maybe you are looking for