Linking a programmatically created folder in SharePoint Document Library.

I have created folders within a document library using InfoPath & C#. To that folder I uploaded several documents using several file attachment controls within the same InfoPath Form using the code behind the form. Now I want to create an Hyperlink
to each folder in another document folder's column that has the relationship with the previously created folder.
When I googled I saw there are lot of articles to create Folders ,uploading documents to folders in a SharePoint Library but I cannot understand how to create a hyperlink in a SharePoint Document Library field column.
Could someone help me to solve this matter?
Thanks,
Regards,
Chiranthaka

Why don’t you create a hyperlink column to store the hyperlink value, or you can use a lookup column to lookup the related folder item?
Qiao Wei
TechNet Community Support

Similar Messages

How to check for the sub folder in the document library Is already Exist using CSOM?

Hi,
My requirement is to create the folder and sub folder in SharePoint document library. If already exist leave it or create the new folder and the subfolder in the Document library using client side object model
I able to check for the parent folder.
But cant able to check the subfolder in the document library.
How to check for the sub folder in the document library?
Here is the code for the folder
IsFolder alredy Exist.
private
string IsFolderExist(string InputFolderName)
string retStatus = false.ToString();
try
ClientContext context =
new ClientContext(Convert.ToString(ConfigurationManager.AppSettings["DocumentLibraryLink"]));
            context.Credentials =
CredentialCache.DefaultCredentials;
List list = context.Web.Lists.GetByTitle(Convert.ToString(ConfigurationManager.AppSettings["DocumentLibraryName"]));
FieldCollection fields = list.Fields;
CamlQuery camlQueryForItem =
new CamlQuery();
            camlQueryForItem.ViewXml =
string.Format(@"<View Scope='RecursiveAll'>
<Query>
                                        <Where>
<Eq>
<FieldRef Name='FileDirRef'/>
<Value Type='Text'>{0}</Value>
                                            </Eq>
</Where>
</Query>
                            </View>",
@"/sites/test/hcl/"
+ InputFolderName);
            Microsoft.SharePoint.Client.ListItemCollection listItems = list.GetItems(camlQueryForItem);
            context.Load(listItems);
            context.ExecuteQuery();
if (listItems.Count > 0)
                retStatus =
true.ToString();
else
                retStatus =
false.ToString();
catch (Exception ex)
            retStatus =
"X02";
return retStatus;
thanks
Sundhar

Hi Sundhar,
According to your description, you might want to check the existence of sub folder in a folder of a library using Client Object Model.
Please take the code demo below for a try, it will check whether there is sub folder in a given folder:
public static void createSubFolder(string siteUrl, string libName, string folderServerRelativeUrl)
ClientContext clientContext = new ClientContext(siteUrl);
List list = clientContext.Web.Lists.GetByTitle(libName);
CamlQuery camlQuery = new CamlQuery();
camlQuery.ViewXml =
@"<View Scope='RecursiveAll'>
<Query>
<Where>
<Eq>
<FieldRef Name='FSObjType' />
<Value Type='Integer'>1</Value>
</Eq>
</Where>
</Query>
</View>";
//camlQuery.FolderServerRelativeUrl = "/Lib1/folder1";
camlQuery.FolderServerRelativeUrl = folderServerRelativeUrl;
ListItemCollection items = list.GetItems(camlQuery);
clientContext.Load(items);
clientContext.ExecuteQuery();
Console.WriteLine(items.Count);
if (0 == items.Count)
//create sub folder here
Best regards
Patrick Liang
TechNet Community Support

Creating a folder for a document library in SharePoint online

Hello I am looking for a good place to get started on creating a folder for a document library using a powershell script. Thanks in advance for any help.

Here is a guide to creating folders and items in a document library for SharePoint Server/Foundation: Creating SharePoint Folders
and Items with PowerShell. You will need to tailor it to your needs as it's a demo for creating 50,000 items.
That's step 1 and contains the bulk of what you would need to do. Here's an example of connecting to a library in SharePoint Online using CSOM: Office
365 - PowerShell Script to Upload Files to a Document Library using CSOM. You won't be uploading files, but the parts where you connect and get a list are what you're interested in.
Now you'll combine bits from both of these scripts:
1. Connect to SPO
2. Get your list (looks like you need to first get the site collection and then the site)
3. Create a folder
I figure it would look something like this (note I haven't tested this at all):
#Specify tenant admin and site URL
$User = "[email protected]"
$SiteURL = "https://tenant.sharepoint.com/sites/site"
$DocLibName = "DocLib"$FolderTitle = "Example Folder"
#Add references to SharePoint client assemblies and authenticate to Office 365 site - required for CSOM
Add-Type -Path "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\ISAPI\Microsoft.SharePoint.Client.dll"
Add-Type -Path "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\ISAPI\Microsoft.SharePoint.Client.Runtime.dll"
$Password = Read-Host -Prompt "Please enter your password" -AsSecureString
#Bind to site collection
$Context = New-Object Microsoft.SharePoint.Client.ClientContext($SiteURL)
$Creds = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($User,$Password)
$Context.Credentials = $Creds
#Retrieve list
$List = $Context.Web.Lists.GetByTitle($DocLibName)
$folder = $list.AddItem("", [Microsoft.SharePoint.SPFileSystemObjectType]::Folder)
$folder["Title"] = $FolderTitle
$folder.Update();
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

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

Issue trying to use a Sharepoint document library as a network drive on which a software can create and delete content

Hi,
With my colleagues we are using a dictation/transcription software which automatically creates files, moves them from folders to folders and deletes them. Until now, all this was done on a network drive, but the drive will soon be unavailable and
we will eventually have to use a SharePoint document library instead, and I am currently testing this option.
I have created a document library (with no versioning and no check out required) and I mapped it as a drive in Windows Explorer to link the SharePoint folders with the dictation software. Everything seems to work fine except
for one thing: when the dictation software tries to move files from one folder to another, the files are pasted in the destination folder but not deleted from the original folder and an error message pops up saying "delete operation has failed".
So the softaware is able to automatically create new content in the document library but is unable to automatically delete (I can however delete manually through the software interface).
Any idea on what is causing this issue and how to solve it?
Thank you

Hi,
According to your description, my understanding is that the documents cannot be deleted in the original folder when using the software with SharePoint library.
I recommend to verify the things below:
Which credential did you use to map the document library as network drive?
If the credential was windows logon, then I recommend to check if the documents can be deleted in the network drive which was connected to SharePoint library directly.
If the documents can be deleted in the network drive which was connected to SharePoint library, then the issue may be due to the compatibility problem between the software and WebDAV. Then you need to check the issue using third-party software provider.
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Require entry of metadata when creating a folder in a document library

Sharepoint Foundation 2010 -
While users are required to enter metadata when uploading a document, it would be a tremendous help if they were required to enter metadata when creating a folder inside a document library.
Is there a way to force entry of metadata when creating a folder? And if this is possible, can I create different metadata requirements for documents uploaded inside a folder?
Thanks.

Yes, you will need to create a Content Types that inherits the Folder Content Type, and then assign your new Content Type to your library. The following blog post explains how to do this (it was written for 2007 but same applies for 2010),
http://www.sharepoint-guru.com/2007/06/adding-metadata-to-folder.html
You can create additional Content Types to reflect the different types of files, each with their own set of metadata columns and requirements.
Dimitri Ayrapetov (MCSE: SharePoint)

Delivery Error when creating Sharepoint Document Library subscription

Recently we have been having issue with a subscription from a report we have.
We have a report that has been generated and have a subscription from that report to create a PDF document within sharepoint.
Recently the subscription stopped working and we have these errors showing:
A delivery error has occurred. ---> Microsoft.ReportingServices.Diagnostics.Utilities.DeliveryErrorException: A delivery error has occurred. ---> Microsoft.ReportingServices.Diagnostics.Utilities.InvalidExtensionParameter: One of the extension parameters
is not valid for the following reason: Failed to validate the delivery setting PATH.The specified user USERNAME could not be found.
Failed to validate the delivery setting PATH.The specified user USERNAME could not be found
Looking into this, I found a few things but they did not help.
One thing was to install update 5 for SQL server 2012 R2, but that didn't help.
Another thing was saying something about there being 2 user accounts, a claims account and a windows user account, but I couldn't figure out how to make it use the correct account.
I also tried to save it to a Windows File Share, and try to save it to the Sharepoint server side, however that failed stating it couldn't find that path.
Being that sharepoint is tricky with its file store (is there really a location on the server that files are stored, I cant find it) I could not figure it out.
I know I can windows explorer to the file location, \\site\shared documents\Folder but if I go to the web servers that host sharepoint I can't find where this path really is.
Thanks

Hi,
According to your post, my understanding is that you want to get error in accessing sharepoint document library files.
The cause is that the account being used to validate accounts on the production domain had been set to expire the password according to the general domain policy.
Once the account is set to never expire, the issues will disappear.
For more information, you can refer to:
http://kb4sp.wordpress.com/2012/12/05/user-cannot-be-found-shenanigans-one-way-active-directory-trusts-and-sharepoint-2013/
http://blogs.msdn.com/b/cliffgreen/archive/2013/02/19/sharepoint-2013-the-directory-is-not-a-subdirectory-of-the-root-directory.aspx
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Can't create Sharepoint Document Library Subscription

I can’t create Document Library Subscription in sharepoint as I get below error message:
A delivery error has occurred. ---> Microsoft.ReportingServices.Diagnostics.Utilities.DeliveryErrorException: A delivery error has occurred. ---> Microsoft.ReportingServices.Diagnostics.Utilities.InvalidExtensionParameter:
One of the extension parameters is not valid for the following reason: The delivery path is either not a SharePoint Document Library Folder or does not exist in the Share Point farm.
Can you please help?
Many Thanks.

This looks like a common problem for this issue:
http://blog.fpweb.net/resolving-ssrs-subscription-issues-in-sharepoint/
See if that is true for you.
Trevor Seward
Follow or contact me at...
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Create a new document in Sharepoint Document Library/OneDrive on iPad/Safari

Hi,
My users are having trouble creating a new document from OneDrive in Safari on their iPads. The screen goes grey like its going to show the popup to select the new file type, but the popup never comes up. If they clear their cache, it works for exactly 1
time and then goes back to this behavior. I'm not exactly sure if it worked before and/or when it stopped working. The iPad I have tested was at the latest 8.2 version of IOS and my Sharepoint farm is an On-Prem install of 2013 with SP1 mark2. My WAC farm
is also 2013 SP1.
Any suggestions?
Thanks,
Matt

Hi,
I understand you are suffering the issue when create a document in Sharepoint Document Library/OneDrive on iPad.
According to the official article
https://technet.microsoft.com/en-us/library/fp161353.aspx?f=255&MSPPError=-2147217396, the version of your iOS should be in the supported list. I guess the issue may start after you installed an update, and if there is any other version (low versions)
of iPads in your company, please use a different version device to test the issue.
Meanwhile, to determine whether the issue is related to your SharePoint environment, I suggest you just to register an Office 365 trail account, and test the issue with SharePoint Online. In case the same issue happens with SharePoint Online, the issue should
be related to your client device, and my next suggestion is to contact support of your device manufacture.
Once you need any help from SharePoint end, please don’t hesitate to come back, and we are always happy to support you.
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]

Attaching Attributes to Image For Loading to SharePoint Document Library

We currently have a need to create a searchable document library which will consist solely of images. The standard metadata for a file/image won't suffice in this case. We have some custom attributes that will need to be searchable.
Essentially, we will have a library of receipt images for expense reporting purposes. We get these images from a third party who handles all of our expense reporting. There are two large zipped files we receive: one file contains all the actual expense report
"data" that was processed that day(amount, date, client, job, etc.) and the second file contains all the receipt images for those expense report items. Each data file contains data for individual expense reports, and each expense report is assigned
a unique ID. Each line item in an expense report is also assigned a unique ID. Lastly, each receipt image for a line item of a specific expense report is also assigned a unique ID.
The zipped image file only contains images. There is a main image file - this contains several smaller zipped files. Each of the smaller zipped files contains all receipt images for a specific expense report. Each image file name is comprosed of three parts:
The expense report identifier, the unique image identifier, and the expense report line item identifier.
So, to put this all into perspective:
On Thursday, we received an image file named extract_images_p006320452r3_20140904171423
This file contained images for the following unique expense reports:
The compressed file 95FB8C488519427793FC contains the following receipt images:
The "data" file - as mentioned before - contains the actual info about the expense and image. These include: date of transaction, date approved, vendor, amount. GL code, type, function, client, project, billable or not, and several other attributes.
All of this information - including the location of the images - is stored in a SQL Server database and then placed in an SSAS cube.
The images are related back to the underlying data via the expense report id, and line item id.
What I need to be able to do is to somehow "tag" these images with all their underlying attributes, load then into a SharePoint document library, and make them searchable.
I have already figured out that I would need to create several SharePoint lists based on the available values in my OLAP cube (essentially a dataset each for clients, vendors, etc.). The part I have no idea how to accomplish is how to tag each image with
its respective information.
All the pertinent info is stored in the database tables, just don't know how to attach it to each image.
Hopefully, this made some kind of sense. If anyone has any idea on how to even remotely accomplish such a thing, your input would be greatly appreciated!
Thanks in advance!
A. M. Robinson

You will have to develop a custom solution to do this. I am assuming you have taken the first steps to define separate document libraries for the expense reports and images along with site columns and contenttypes. You would define the site columns based
on the data you want to search on and assign these to corresponding contenttypes. So basically a contenttype for expense reports and receipts possibly. You would link the two contenttypes using the expense report id.
Your custom solution would have to break apart the zip files and upload and index (set site column data) for each file. Then the user could search on the expense report id and get all the files associated with the expense report.
An alternative could be to use one document library and have all the files uploaded into their own document set (folder).
Blog | SharePoint Field Notes Dev Tools |
SPFastDeploy | SPRemoteAPIExplorer

Ssrs sharepoint 2013 error: "A delivery error has occurred ...not a sharepoint document library..."

Greetings SSRS/SharePoint experts,
SharePoint 2013 with SSRS - Creating a subscription to a report that is in SharePoint
I'm trying to create a subscription to publish a report to a sharepoint document library.
I've configured all the settings and on clicking OK get the following error:
"A delivery error has occurred. ---> Microsoft.ReportingSerives.Diagnostics.Utilities.DeliveryErrorException: A delivery error has occurred. ---> Microsoft.ReportingServices.Diagnostics.Utilities.InvalidExtensionParameter: One of the extension
parameters is not valid for the following reason: The delivery path is either not a SharePoint Document Library Folder or does not exist in the Share Point farm."
SQL Server Developer Edition 2012 SP1
SharePoint 2013 Standard
Just wondering if anyone has a solution.
I've tried changing the proxy settings as per this post
http://social.technet.microsoft.com/Forums/en-US/19817dc7-6725-40d8-befa-1b94099a71bd/sql-server-2012-reporting-services-in-sharepoint-2013-integrated-mode-dilivery-extension
Workaround is to not use a sharepoint document library but write the report to a windows file share (this works but is not optimal).
Hoping someone at Microsoft or an expert will come back with something.
Kind regards
Gio

Hi,
Can you check the SharePoint ULS log located at : C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS, and look at the log there when the error occurs?
You can also check the Application Event Log on the SQL Server to see if there are any additional errors.
Tracy Cai
TechNet Community Support

Adding a Sharepoint Document Library in Windows Explorer Fovorites

I want to add a sharepoint document library in my favorites in windows explorer... Every time I copy the link, instead of opening the library in windows explorer, it open the browser and go directly to the site... Any help would be appreciated.
Thanks in advance,
Sebastien

Hi Seabass:
Have you tried mapping the library in question as a network location on your local machine?
http://windows.microsoft.com/en-us/windows/create-shortcut-map-network-drive#1TC=windows-7
To map to a particular SharePoint resource on your site, you would use this structure:
\\mysharepointsite@80\sites\library\Photos as your network address.
In this manner, you can add this link to your Favorites, and you will have the Windows Explorer mode you're requesting. Hope this helps! ;)

Download older version of a file from SharePoint Document Library using CSOM and 404 error

Hi,
I am trying to download previous versions including Major and Minor versions of documents from SharePoint Online using CSOM. I get 404 error when I try to download the file. I found several posts on various discussion forums where people are getting same
error but none of those have any solution/answer. Below is one of the threads and sample code I have tried that results in 404 error. If I use the link in browser directly, I am able to download the file. Also I am able to download the current version of file
using CSOM without any problem, it is only the older versions that give me 404 in CSOM.
http://qandasys.info/how-to-download-the-historical-file-version-content-using-csom/
public int GetStreamFromFile(string docid, string lib, string fileurl, ClientContext clientContext, int iuserid, string Version, bool isCurrrent)
if(!isCurrent)
List LibraryName = clientContext.Web.Lists.GetByTitle(lib);
clientContext.Load(LibraryName);
clientContext.ExecuteQuery();
CamlQuery camlQuery = new CamlQuery();
camlQuery.ViewXml = "" + fileurl +
Microsoft.SharePoint.Client.ListItemCollection collListItem = LibraryName.GetItems(camlQuery);
clientContext.Load(collListItem, items => items.Include(item => item.Id, item => item["FileLeafRef"], item => item["LinkFilename"],
item => item["FileRef"], item => item["File_x0020_Size"], item => item["DocIcon"], item => item.File.Versions));
//clientContext.Load(collListItem);
clientContext.ExecuteQuery();
foreach (Microsoft.SharePoint.Client.ListItem oListItem in collListItem)
//string fileurl1 = (string)oListItem["FileRef"];
//string filename = (string)oListItem["LinkFilename"];
foreach (FileVersion version in oListItem.File.Versions)
if (Version == version.VersionLabel)
//Added excutequery to get object one more time as per blog
//http://social.technet.microsoft.com/Forums/de-DE/sharepointdevelopmentprevious/thread/88a05256-8694-4e40-863d-6c77512e079b
clientContext.ExecuteQuery();
FileInformation fileInformation = ClientOM.File.OpenBinaryDirect(clientContext,version.Url);
bytesarr = ReadFully(fileInformation.Stream);
Darwaish

Hi,
According to your description,
I know you want to get older version of a file from SharePoint Document Library using Client Object Model.
The following code snippet for your reference:
public void GetVersions()
ClientContext clientContext = new ClientContext(“http://SPSite”);
Web site = clientContext.Web;
clientContext.Load(site);
clientContext.ExecuteQuery();
File file = site.GetFileByServerRelativeUrl(“/Shared Documents/mydocument.doc”);
clientContext.Load(file);
clientContext.ExecuteQuery();
ListItem currentItem = file.ListItemAllFields;
clientContext.Load(currentItem);
clientContext.ExecuteQuery();
FileVersionCollection versions = file.Versions;
clientContext.Load(versions);
clientContext.ExecuteQuery();
if (versions != null)
foreach(FileVersion _version in versions)
Console.WriteLine(“Version : {0}”,_version.VersionLabel);
More information:
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.client.file.versions.aspx
Best Regards,
Dennis Guo

Advice needed for provider hosted web application - authentication and access to SharePoint document library

I haven't done SharePoint 2013 development with claims so I apologize in advance if my assumptions and questions are way out in left field.
I'm trying to understand SharePoint 2013 claims authentication for a scenario that involves:
A SharePoint provided hosted (web forms) app that will pull information and assets (e.g. PDFs) from SharePoint into the web page.
It will be a VS 2012 solution with asp.net.identity feature.
Security will be set for internal users, federated external users and forms-based external users. Based on their security and (claim type) role it will define what information and assets that can be retrieved from SharePoint
I have looked through MSDN and other sources to understand.
This one helped with my understanding
Federated Identity for Web Applications and assumed that the general concept could be applied to forms-based identity for non-Federated external users .
What I have now:
VS 2012 solution web forms application set to Provider Host with asp.net.identity feature and its required membership tables.
I can create new users and associate claims to the new user.
I can log in with a user from the membership tables and it will take me to a default.aspx page. I have added code to it that displays the claims associated to a user.
For POC purposes I'd like to retrieve documents that are associated to this user from the default.aspx page.
This is where I am having trouble understanding: Is my understand correct?
Internal users
since they are internal on the network i am assuming that they would already have access to SharePoint and they would already be configured to what documents that they have available to them.
Federated external users & Forms authentication external users
it seems to me that the authentication for external users are separate from SharePoint authentication process.
changes to the configuration settings are necessary in SharePoint, IIS, web application.
I believe this is what i read.
claims processes (e.g. mappings) need to be set up in SharePoint
as long as external users are authenticated then things are ok b/c they would have claims associated to the user and the configuration in SharePoint takes are of the rest.
This statement bothers me because I think it's wrong.
So basically i'm stuck with if my understanding is correct: once a user is authenticated either by federated identity or asp.net.identity authentication that it should go to the provider hosted default.aspx page because the claim is authenticated and means
that it should have access to it and the SharePoint document library based on some claim property. I could then write the calls to retrieve from a document library and SharePoint will know based on some claim property that the logged in user can only
access certain documents.
It just sounds too good to be true and that i'm missing something in the thought process.
Thanks in advance for taking the time to read.
greenwasabi

Hi GreenWasabi,
i agree this is an interesting topic to discuss,
as you can check from the article, you may check this example from the codeplex:http://claimsid.codeplex.com/
when i thinking regarding this topic, its looks like an environment with multiple of realms,
from what you understand, its correct that all the authentication is based from the provider, so for example i have a windows live ID and internal ID, then when i login windows live ID, it will be authenticated using windows live ID server.
here is the example for the webservice:
http://claimsid.codeplex.com/wikipage?title=Federated%20Identity%20for%20Web%20Services&referringTitle=Home
as i know, if you using this federated, i am not quite sure that you will need to go to the provider page literally, perhaps you can check this example if we are using azure:
http://social.technet.microsoft.com/wiki/contents/articles/22309.integrating-windows-live-id-google-and-facebook-accounts-with-sharepoint-2013-white-paper.aspx
Regards,
Aries
Microsoft Online Community Support
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Word opening in Client Application in SharePoint document library when feature is not activated in manage features in site collection

Hello, I wish for all Word documents to open in the browser for my SharePoint document library on my team site.
The feature 'open in client application' is not activated in Features for the site collection and the setting in the document library is set on 'Use the server default (open in the browser)
When I select File > new> from the ribbon in the document library - it still opens Word in the client application?
Any ideas on this?
Is there a general Office 365 setting over riding SharePoint somewhere?
Regards
kegan1

Okie don't open up a ticket. Can you please open internet explorer...See if its the latest version. Once you have done that can you login to the SharePoint site. Then go to the internet wheel option in top right corner > select manage add on >
Click on toolbars and extensions on left > then click on SharePoint open documents in client and disable it. Close the browser completely now for the changes to take effect. Open internet explorer once again and then try to go to site collection click on
file and create new. The word will open up in browser now. This has to be done on each and every machine in your firm so that users will be able to open up only in browser. Out of the box there is only one way is to customize the ribbon and remove the new
option from there or creating an all together new ribbon for your SharePoint from visual studio.

Linking a programmatically created folder in SharePoint Document Library.

Similar Messages

Maybe you are looking for