I have a bit of challenge. Knowing only the basic URL for the sharepoint installation, can I get a list of the site collections that have been created using only the basic web services that are installed?
Using the Webs web service or the SiteData web service I've been able to get information on the default site collection that's at the base URL (http://MySharePointServer/). I can also get a full list of sites below the site collection and a description of the site collection itself but I can't seem to get any info on the other site collections under the same web application.
Any help would be appreciated, I thought it would be a piece of cake to get the info.
Unfortunately, no. That functionality isn't available from the out-of-the-box web services. The only option that might work is using the Search Web Service (I'm not familiar enough with it to know).
This walkthrough describes how to add your own custom web services to the product. I strongly recommend this approach as it's very likely there will be other missing functionality you will need to add - if not now, in the near future.
Related
Is it possible to create an HTTP get the request that is sent from SharePoint online and retrieve the data and save it to the SharePoint site in documents?
I do this locally now, and it looks like you can do it with the SharePoint server on an on-premises installation. but I'm not sure about SharePoint online.
Is it possible to run the script as a service on SharePoint online, the way I do locally?
I know I can do something like this with azure so that the whole installation is cloud-based, but I would like to do it on SharePoint online, just for simplicity's sake without the added maintenance, plus we aren't doing anything other than basic file retrieval.
also, any information about scripting in SharePoint online would be helpful. from the documentation I've seen, I can't tell that SharePoint online has this capability.
any help would be great.
It's not possible to run server-side services such as timer jobs on SharePoint Online. All custom logic will "move down" to the client computer, or "move up" to a local server outside the SharePoint farm or SharePoint Online subscription.
Keeping custom code off SharePoint online could prevent the custom code from harming their servers or reduce the performance of their SharePoint Online websites.
BR
My company switched from an onsite SharePoint 2013 to SharePoint Online.
I had some pages that consisted of multiple web parts, including the filter web parts.
I've rebuilt these pages in Sharepoint Online, but none of the filter web parts are available.
Every list is set to use classic experience - except the site itself, which I do not have control over.
According to IT support these specific filter web parts are simply not available in SharePoint Online, and therefore they can't help me.
I honestly don't trust that answer completely, which is why I'm asking here ;-)
So:
Can the filter web parts be made available for classic view in Sharepoint Online?
Suggestion on what would need to be configured in order for these to be made available?
Possible links to official Microsoft documentation?
Thanks :-)
Per my test, the filter web parts are available in SharePoint Online. As the below picture shows:
You could donot have access to the web part gallery. Ask the site admin to give your access to the web part gallery: please go to site settings-> Web parts, grant the user access to the library.
Iam trying to develop webpart for firm website on SharePoint with visual studio, the problem is that there is no solution for SharePoint online - Visual web part. When i try to create SharePoint 2013 - visual web part, I get an
error message.
The only thing there is for Sharepoint online is Apps for Sharepoint and that isn't a web part, or atleast I haven't found a way to use it as such.
When I talk to my supervisor about the error, he tells me that they can't create a virtual server for me to install the SharePoint server on and I have to code it through the Sharepoint online.
Is there any way for me to develop and deploy the webpart with an online Sharepoint server instead of local one or to atleast create it through the apps for Sharepoint?
You can use App Parts, those are Web Parts that display content from an installed App, you can add them at any page of your site as normal Web Parts, App Parts are deployed in the same package as your App, so you can have everything in the same solution.
There are plenty of resources that will help you to develop Apps and to include App Parts also, just look for the right concept in google and you will find it.
There are two kinds of SharePoint Apps (or Add-ins which is the new name), the first one is SharePoint Hosted App and the second one is SharePoint Provider Hosted App, the one you need will depend on the functionality you want to achieve, but as a general reference you can think on the data source that you want to consume in your solution, e.g. if the data to be used by the App is in the SP Site where you are going to install it, then all you need is a SharePoint Hosted App, however if the data is in an external location like databases stored in local servers, then you will need SharePoint Provider Hosted App. Of course this is just a very basic view of this topic, there are other reasons to use one or the other but its pointless to make a full list here. This is a wide topic and you can find tons of articles and guides about this.
If all you need is a simple webpart to display some content with a nice look or roll up some content and provide an output based on it, then you can use a SharePoint Hosted App, which is the easiest to develop and deploy, with this kind of app you can use JavaScript get the data from your site, and then you can display your output in an App Part.
I'm sorry to not provide specific pages to read, but that's just because it's better to look for the guides that be easier for you to understand and that may vary from person to person, all you need to know is the concepts and topics to search for.
If you want me to help you with this please send me a message (my profile).
We are in the process of moving an on-premise SharePoint installation to SharePoint Online. We have a number of existing C# web parts that we need to convert. These web parts currently access some of our on-premise data... we need to get the web parts working on SharePoint Online; however, we're not certain of the best approach.
We've looked at BCS, but it seems that it is geared more towards synchronizing lists of data via basic CRUD methods. For many of our applications, we are not looking to synchronize lists, we are looking more towards action-oriented methods on a service that can be called on-demand as needed by the web part.
We don't believe the call can be client-side, as the users will often be accessing SharePoint Online from workstations that are not joined to our domain, and we don't want the user to have to separately authenticate to our service (i.e. we want our service to trust only the SharePoint Online backend).
Our ideal setup would be to have our C# code for the web part call into our web service (hosted on our domain, authenticating with a service account from the SPO secure store), passing the current username from the SharePoint context, and getting back a response that the web part can then use for its processing.
But as we understand, the web parts in SharePoint Online are sandboxed in such a way that they cannot make external HTTPS calls via HttpWebRequest.
We've searched for how-to examples or documentation related to our use case, and haven't found anything saying it's possible or that it's not possible. Does anybody know if it's possible for a web part to get data in this way? Is there some other direction we should be taking to achieve this?
In SharePoint online, if you are developing a SharePoint hosted app; You will be able to call external endpoints (EPs) after adding these endpoints in the manifest file.
If you haven't added these endpoint to the manifest file, This means you are not permitting the app to call an external EPs.
You don't need BCS in SharePoint online to call external EPs. Here is a sample on how to do this using JavaScript.
https://msdn.microsoft.com/en-us/library/office/fp179895.aspx
Let me know if you have any other questions.
I am building out a redesign of our corporate intranet on sharepoint 2010. We have three web applications: My sites, Team or Organization sites, and the Intranet “portal”.
On the intranet I want to read lists from Team sites of type announcements and calendar and aggregate them together. Then, on the Intranet, I’d like to have some editorial control as to what actually shows up. By default, I’d like list items to show up on the intranet, but would also like to be able to hide or delete them if deemed not important enough.
Would I benefit from using a publishing portal for the Intranet?
Would it make sense to write a web part to read the lists, sync the lists into a new list on the intranet, and then the content manager could uncheck the ‘display’ check box?
What is the best way to implement this type of infrastructure?
Where’s the documentation?
As I understand it you're wanting to syndicate lists from you Team/Organisation sites.
For this you could use a Data View Web Part connected to the lists.asmx webservice of the teams/orgs web app for a middle tier approach. You could include a field on your content types in the teams/orgs web app to indicate if a record should show on the intrnet and include that in your query when retrieving items.
As to using Publishing..... Will you have traditional web pages in your intranet? if so, then yes, use it, if not then I can't see a huge benefit.