SharePoint Online list data being "read" slowly by third-party application

%3CLINGO-SUB%20id%3D%22lingo-sub-2704702%22%20slang%3D%22en-US%22%3ESharePoint%20Online%20list%20data%20being%20%22read%22%20slowly%20by%20third-party%20application%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2704702%22%20slang%3D%22en-US%22%3E%3CP%3EOur%20University%20uses%20Sitecore%20as%20our%20Web%20CMS%20and%20we%20have%20a%20%22dataset%22%20component%20that%20is%20used%20to%20read%20data%20from%20lists%20and%20libraries%20and%20render%20it%20on%20pages%20in%20Sitecore.%20This%20was%20created%20probably%2010%20years%20ago%20for%20SharePoint%202010.%20We've%20since%20moved%20from%20SP2010%20to%20SP%20Online%2C%20migrating%20(with%20Sharegate)%20the%20lists%20and%20libraries%20that%20needed%20to%20be%20rendered%20through%20Sitecore.%20It's%20been%20working%20OK%20for%20over%20a%20year%20(at%20least%2C%20folks%20haven't%20been%20complaining%20about%20it)%2C%20but%20recently%20we%20found%20that%20a%20couple%20of%20lists%20are%20taking%20more%20time%20than%20expected%20to%20refresh.%20There%20are%20two%20in%20particular.%20One%20is%20fairly%20large%2C%20with%20lots%20of%20text%20data%2C%20so%20the%20~47%20seconds%20it%20takes%20for%20initial%20load%20is%20almost%20acceptable.%20The%20other%20is%20fairly%20small%3A%20the%20list%20has%20a%20total%20of%2021%20rows%2Fitems%20and%20about%202%20dozen%20columns%20(mostly%20text%2C%20but%20one%20lookup%20with%20three%20%22additional%22%20columns%20coming%20with%20it).%20The%20odd%20thing%20about%20this%20one%20is%20that%20it%20was%20created%20as%20a%20duplicate%20of%20another%20list%20(using%20the%20%22from%20an%20existing%20list%22%20option%20when%20creating%20a%20list)%20and%20the%20original%20list%20is%20loading%20without%20issue.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%2C%20I'm%20not%20the%20creator%20of%20this%20dataset%20component%2C%20and%20I'm%20not%20a%20developer%2C%20so%20I%20have%20no%20idea%20how%20it's%20constructed.%20However%2C%20knowing%20that%20it%20was%20developed%20for%20SharePoint%202010%2C%20it's%20almost%20certainly%20using%20legacy%20api%20calls%20to%20get%20the%20data.%20As%20an%20aside%2C%20we%20bypassed%20SP2013%20and%20went%20straight%20to%20SPO%2C%20so%20the%20notion%20of%20rebuilding%20this%20to%20use%20the%20REST%20api%20never%20occurred%20to%20the%20developers.%20They%20found%20that%20they%20could%20just%20add%20a%20new%20%22server%22%20for%20SPO%20and%20it%20worked.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyway%2C%20are%20any%20other%20folks%20still%20using%20other%20apps%20to%20interface%20with%20SPO%20data%20via%20asmx%20services%3F%20If%20so%2C%20are%20you%20also%20seeing%20slow%2Fdelayed%20responses%20from%20them%3F%20I%20know%20this%20is%20kind%20of%20a%20long%20shot%2C%20but%20worth%20the%20ask.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2704702%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2010%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELists%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Regular Contributor

Our University uses Sitecore as our Web CMS and we have a "dataset" component that is used to read data from lists and libraries and render it on pages in Sitecore. This was created probably 10 years ago for SharePoint 2010. We've since moved from SP2010 to SP Online, migrating (with Sharegate) the lists and libraries that needed to be rendered through Sitecore. It's been working OK for over a year (at least, folks haven't been complaining about it), but recently we found that a couple of lists are taking more time than expected to refresh. There are two in particular. One is fairly large, with lots of text data, so the ~47 seconds it takes for initial load is almost acceptable. The other is fairly small: the list has a total of 21 rows/items and about 2 dozen columns (mostly text, but one lookup with three "additional" columns coming with it). The odd thing about this one is that it was created as a duplicate of another list (using the "from an existing list" option when creating a list) and the original list is loading without issue. 

 

Now, I'm not the creator of this dataset component, and I'm not a developer, so I have no idea how it's constructed. However, knowing that it was developed for SharePoint 2010, it's almost certainly using legacy api calls to get the data. As an aside, we bypassed SP2013 and went straight to SPO, so the notion of rebuilding this to use the REST api never occurred to the developers. They found that they could just add a new "server" for SPO and it worked.

 

Anyway, are any other folks still using other apps to interface with SPO data via asmx services? If so, are you also seeing slow/delayed responses from them? I know this is kind of a long shot, but worth the ask.

0 Replies