June: SharePoint Web Services

Quam speciem populus ut a quaero PROPOSITUM / Content Usura Source Sharepoint 2013 CETERA API

2 Restituo

I had reason to work with the SharePoint 2013 Search API via REST for the first time. I wanted to search for people, not documents. The key learning here is that you specify content sources via its GUID (or at least in this case). The following jQuery snippet shows how:

    loadExpertsAsync: munus() {

        jQuery.support.cors = verum;

        $.ajax({
            url: hoc.CreateFullApiUrl() +
                "?querytext='portals'&sourceid='b09a7990-05ea-4af9-81ef-edfab16c4e31'" +
                "&selectproperties='LinkedInProfileUrl,GoogleCirclesProfileUrl,BALargeProfilePictureUrls,BAGridPictures,WorkEmail,Skills,AboutMe,Interests,JobTitle,PastProjects,PictureURL,PreferredName,TwitterHandle,LinkedInProfileUrl,PreferredName,GoogleCirclesProfileUrl'" +
                "&rowlimit=99",
            methodo: "GET",
            headers: { "Accept": "application/json; odata=verbose" },
            cache: falsum,
            success: munus (result) {

In meam, I’m running the API against SharePoint online. To get the GUID, I followed these steps:

  1. Access the SharePoint admin center
  2. Select “search” from the left hand navigation
  3. Select “Manage Result Sources”
  4. Select “Local People Results”
  5. Look at the URL.

My URL looked something like:

https://xyzzy-admin.sharepoint.com/_layouts/15/searchadmin/EditResultSource.aspx?level=tenant&sourceid=b09a7990%2D05ea%2D4af9%2D81ef%2Dedfab16c4e31&view=1

The sourceid parameter is what worked for me.

(I understand that the sourceid may actually be a sort of permanent thing with SP, but I’ll always check anyway 🙂 ).

</finem>

undefinedScribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

Lists.asmx, GetListItems folders

6 Restituo

Ego faceret investigationis aliquis hodie circa list.asmx telam servitio dummodo ut pars SharePoint 2010 (et superius).  Potuit ut album items in radix folder (possidet nomina sub-folders), sed non posset items in sub-folders.  Ego respiciens in aliquo internets et suus mirae soletquaeri.  Tamen, Ad bene non posset de facili, "Si ego noui folder, quomodo illuc vasa folder?"  Ad esse honestum, Quia non habeo uelle experiri facile instar omnium mihi super hoc tempus risus.

Usque ad explicanda, Ego creavi a site nomine "blogging Missionibus" et consuetudo nomine album "Lorem List cum ulterius folders".  Ergo ego creavi nomine folders:

  • Anno 2005
  • Anno 2006
  • Anno 2007

Ego addidit paucos items ut folder "Anno MMVI".  Hoc est quod similis:

image

Amicus meus est non scribere sed usura C # Codicis Java, ita saponem involucrum quod vere opus erat.  Ut quod, Aliquid scripsi et frenum of usus jQuery fiddler ut HTTP actuali conuersatione.

Hic 'pertineret jQuery (Descripsi codice infra si vis ad effingo / crustulum):

image

Primo utrumque ponitur a key est <queryOptions> et <QueryOptions> node.  Secunda est quod clavem <Folder> node est URL quod client accessum habet.

Ut hoc sit alia, Sed hoc bene faceret propter me cum usura jQuery.

Hic est enim supra saponem involucrum:

<soapenv:Involucrum xmlns:soapenv =’http://schemas.xmlsoap.org / saponem / involucrum /’>                
  <soapenv:Corpus>
    <GetListItems xmlns =’http://schemas.microsoft.com / sharepoint / saponem /’>
      <listName>Sub consuetudine album folders</listName>
      <viewFields>  
        <ViewFields>
          <FieldRef name = 'Title’ />
          <FieldRef name = 'EncodedAbsUrl’ />
        </ViewFields>
      </viewFields>
      <queryOptions>
        <QueryOptions>
          <Folder>http://demoserver1/Blogging Scenarios / Libelli / Lorem List cum folders Sub / anno MMVI</Folder>
        </QueryOptions>
      </queryOptions>
    </GetListItems>
  </soapenv:Corpus>
</soapenv:THECA>

Lorem circa ea ipsa figura credam mihi satis tractatum est <QueryOptions> et specificare nomen folder.  Enim me, EGO postulo ut intus et conturbaverunt eam <queryOptions> necnon specificare satis idonei URL pro <Folder> node.

Hic 'jQuery Nullam setup:

$(document).paratos(munus() {
       = erat soapEnv
           "<soapenv:Involucrum xmlns:soapenv =’http://schemas.xmlsoap.org / saponem / involucrum /’> \
               <soapenv:Corpus> \
                    <GetListItems xmlns =’http://schemas.microsoft.com / sharepoint / saponem /’> \
                       <listName>Sub consuetudine album folders</listName> \
                       <viewFields> \
                           <ViewFields> \
                              <FieldRef name = 'Title’ /> \
                              <FieldRef name = 'EncodedAbsUrl’ /> \
                          </ViewFields> \
                       </viewFields> \
                       <queryOptions> \
                         <QueryOptions> \
                           <Folder>http://demoserver1/Blogging Scenarios / Libelli / Lorem List cum folders Sub / anno MMVI</Folder> \
                         </QueryOptions> \
                       </queryOptions> \
                   </GetListItems> \
               </soapenv:Corpus> \
           </soapenv:THECA>";

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

Lists.asmx, GetList et "Value potest non esse nulla”

1 Respondere

Ego inventa hodie quod GetList() Modus lists.asmx telam ministerium vocari exactissime aut pronus suus deberet iaculari arcanam "value non potest esse nulla" exceptione (et ut 'assumens te possit praeteritum in deterius generis erroris nuntius, “Exception of type ‘Microsoft.SharePoint.SoapServer.SoapServerException’ proiectus. ")  Specie, Praefigunt deprehendi non possunt in qualibet GetList elit.  Puncto sequenti jQuery snippet illustrat:

image

Quod si feceris,, textus muneris respondet "value non potest esse nulla", ut per hoc fiddler-dummodo HTTP transcript:

<?xml version="1.0" encoding="utf-8"?>
  <saponem:THECA
     xmlns:saponem ="http://schemas.xmlsoap.org / saponem / involucrum /"    
     xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
     xmlns:xsd ="http://www.w3.org/2001/XMLSchema">

  <saponem:Corpus>
    <saponem:Vitium>
      <faultcode>saponem:Servo</faultcode>
      <faultstring>
        Exception of type ‘Microsoft.SharePoint.SoapServer.SoapServerException’ Missum.
      </faultstring>
      <detail>
        <string = error xmlns"http://schemas.microsoft.com / sharepoint / saponem /">
Valorem non potest esse nulla.
        </errorstring>
      </detail>
    </saponem:Vitium>
  </saponem:Corpus>
</saponem:THECA>

Utique, vos probabiliter quod non addunt 's0' praepositione in vestri own, Sed quaedam instrumenta sunt proni ad facere (sicut Eclipse).

Hoc multo magis perversa / irrita, quia aliis modis tolerare praefixis.  Puta, in GetListCollection Lorem praefixa animum si modum non, etiam cum praefixis sicut deliramentum verba "xyzzy":

image

Hoc "value non potest esse nulla" Videtur satis communis ita Hopefully is mos succurro quispiam de cetero lists.asmx.

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin