SOAP
2 TopicsUpdateListItems -List no longer exists SOAP 0x81020026
We have a an old SharePoint integration to our system, and we want to migrate the SharePoint 2013 into SharePoint online, but after we migrate the data the UpdateListItems calls won't work anymore... even the read calls woks fine and the user can manipulate data through SharePoint website. (I created a new list, with the same user, add a row, and try to modify it via SoapUI, same result...) <ErrorCode>0x81020026</ErrorCode> <ErrorText>The list that is referenced here no longer exists.</ErrorText> <z:row ows_ID="1" ... Any suggestion/guess would be helpful.932Views0likes0CommentsSharePoint 2010 to 2016 Migration - Feature Compatibility - SOAP Web Services
SharePoint 2016 still includes the SOAP/ASMX Web Services however we understand that they are still supported but deprecated. https://docs.microsoft.com/en-us/sharepoint/dev/general-development/choose-the-right-api-set-in-sharepoint#DeprecatedAPIsus/sharepoint/dev/general- development/choose-the-right- api-set-in-sharepoint# DeprecatedAPIs The client has a utility application that interacts with the Web Services in their current SharePoint 2010 environment. This external utility cannot be updated during the upgrade from 2010 to 2016 to use the preferred CSOM or REST APIs. Understandably in 2013 they are not deprecated but SP2013 will go out of support much sooner than 2016. We would like to, therefore, recommend 2016. Is there a risk that the SOAP/ASMX Web Services will be removed as part of an update to SP 2016 or is it safe to assume that the Web Services will remain as part of SP 2016 and won't be made obsolete until the 2019 release of SharePoint?2.7KViews0likes2Comments