Hot answers tagged web-services
2
The actual mechanism would vary considerably based on the intended usage of the data but the basic choices are:
leverage Business Connectivity Services which would expose the
DB2 data to Sharepoint almost as if it were a built-in list.
create custom Web Parts that query the database or the web services.
use javascript to fetch the data directly on the ...
1
You could use some nice work around.
The first solution that you could implement is working with the GUID of the list and the column instead of the title.
Or you can deploy a service that you can ask for the list and it'll reply to you with the name of the list translated in the current language.
1
As you have seen, the limit for the Query is actually 2048 characters. So any more than that will throw this exception.
http://stackoverflow.com/questions/8061330/how-to-overcome-fast-search-char-limitation-2048 is a possible duplicate of your question, but sadly it never recieved any attention.
Also this from Technet ...
1
A web part is for displaying content, not to provide a content repository for other components. A few options:
Perhaps you don't need a web part at all, just create a list and store the image there.
Perhaps you also need a web part. Create a list, store the image there, and reference that image from the web part. Other components could then also reference ...
1
If its just about getting webpart content from an accessible page within same domain, I dont think you will need a webservice for it.
You can place your webpart within a div (id=container) and use below Jquery :
$('#result').load('sitepages/test.aspx #container');
When this method executes, it retrieves the content of sitepages/test.aspx, and then jQuery ...
1
I believe you should use XML as input data,
The Power of XmlElement Parameters in ASP.NET Web Methods
What is the best way to send xml data to a web service rather than using CDATA?
1
Problem solved. Sharepoint was setup without the FQDN and although the Web application was working, the REST API was not working and was always retrieving data for the root site.
Using the Central Administrator after the URL was changed to use the FQDN all is fine now and data is retrieved correctly.
Only top voted, non community-wiki answers of a minimum length are eligible
