1

I've supported third party integrations with Sharepoint for different companies using WSDL Soap web services from the SP 2010 and 2013. This has been on their locally installed sharepoint instances.

To do this we have used the WSDL Soap web services:

https://msdn.microsoft.com/en-us/library/ms154052.aspx

We use these wsdl's:

  • Lists.wsdl
  • SiteData.wsdl
  • UserGroup.wsdl
  • Webs.wsdl

Now all the rage is this Office Sharepoint online through the Office 365 portal.

I seem to be getting conflicting reports which of these features will continue to work versus stop working.

And do certain Sharepoint Online plans carry the web service features and others don't?

What quirks/gotchas are going to happen on Sharepoint Online when doing web services work that didn't happen on local installations?

1
+50

I don't have my SP2010 VM open and running right now, I'll check on later, but I think Office 2010 still uses the "old" SOAP services to communicate with SharePoint (since SP2013, Word, Excel... use the new hype REST endpoints).

So, even if they're officialy deprecated, I think you're safe till Office 2010 support period ends... But that's only a guess. Also note that SP2016 still has these SOAP interfaces.

  • Unless I'm missing on what you are talking about, i was asking about Sharepoint online soap web services availability. – Nicholas DiPiazza Dec 23 '16 at 5:39
  • This is what I'm talking about too. As Office 2010 has to be supported with SPO, and as Office 2010 uses .asmx to communicate with SharePoint, my guess is: they cannot remove these .asmx SPO-side unless they're ready to break Office 2010 while it's still supported... – Evariste Dec 23 '16 at 6:41
  • OK @Evariste my trial just finished provisioning I'll start trying it out. thanks. – Nicholas DiPiazza Dec 23 '16 at 13:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.