SOAP Web Services Data Integration with SharePoint

SOAP Web Services​ data can be integrated codeless with native SharePoint lists using the Layer2 Business Data List Connector. Please take a look here for more supported systems and applications. In case you are looking for Online data integration, you will find the right tool here.


sharepoint integration layer2 bdlc

Benefits of SOAP Web Services Data Integration in SharePoint


  • Very easy to setup in a few minutes: Create a SharePoint list, click "Connect to external data source" in the list settings, select the Layer2 Data Provider for SOAP Web Services, enter connection settings and data query as shown below. That's it - no programming, no touch of the external data source, no additional tools.
  • Connected data always up-to-date: The connected data updates automatically in background (via SharePoint Timer Job), or alternatively, on-demand (Action Menu / Ribbon Button, URL, via workflow, API).
  • One-way and optional two-way connection: You can write-back the changes made in SharePoint to the external data source automatically with full CRUD (Create / Update / Delete) functionality. The SharePoint list can act as a full-featured front-end for external systems. Specifically the SOAP data provider is read-only.
  • 100+ external systems supported: Layer2 Data Providers included (e.g. for SharePoint/Office 365, Exchange, Dynamics, OData, XML/RSS, SOAP), vendor specific data providers can be used (e.g. SQL Server Oracle, mySQL etc.), 3rd party data providers also supported, e.g. for ERP/CRMs, Facebook or Twitter. See here for supported systems and applications.
  • Well-known BCS "external list" issues and limitations are completely solved: ALL list features are to you. Views, sorting and grouping, filters, calculated fields, search, managed metadata. Lookups, additional columns and attachments can be created as normal. All kind of lists can be used, e.g. contacts, tasks, calendar, or custom lists. You can take external data offline via Outlook.
  • Workflows and notifications on external data change: List workflows and change notifications per RSS or email can be used to take business actions in SharePoint, when external business data records are changed.

  • Application logging, reporting, and notifications: A SharePoint list ist used to store settings and log information. SharePoint item versioning and workflows can be used to manage reporting and notifications. Direct notification per email in case of errors is supported as well.

  • Highest Security, best performance, easy to maintain: SharePoint Secure Store can be used to store security relevant configuration information safely in one central place. Users are working with the SharePoint lists as an external data cache with highest security and performance.

SOAP Web Services Specific Configuration Settings


​In the Layer2 Business Data List Connector the data source must be configured as follows to connect to a SOAP Web Service.


soap webservice bdlc configuration


Figure 1: Sample connection configuration to connect to a SOAP Web Service.


Please note the following about settings, features and possible issues


  • A typical connection string for the Layer2 Data Provider for SOAP Web Services looks like:
    Url=http://mysourceSite/myrss;User=myUser; Password=myPassword;Protocol=mySoapProtocolVersion
  • The Layer2 Data Provider for SOAP Web Services supports a slightly different syntax than SQL to query the items from the web service like: SELECT [Fields] FROM [Operation]([Parameters])
  • Please find a full specification for the Layer2 Data Provider for SOAP Web Services here.

Do you have any issues to connect? Please contact for next steps.

SOAP Web Services Connection Details


​​Data Provider:
Layer2 Data Provider for SOAP Web Services

Connection string sample:
Url=http://mysourceSite/myrss;User=myUser; Password=myPassword;Protocol=mySoapProtocolVersion

Select Statement sample:
SELECT * FROM myOperation


Or with Parameters:

SELECT * FROM myOperation(parameters)

SOAP Web Services Data Integration Known Issues and Restrictions 


  • ​Note that the data provider is read-only. No write-operations supported.
  • Additional out-Parameters cannot be handled.
  • Operation parameters are of simple type (i.e. string, integer, etc.). Parameters of complex types defined in the WSDL or of type “any” are not supported.
  • The result returned from the operation does not contain multi-occurrence properties. If it does, these properties will be skipped (omitted) and a warning will be raised.
  • The service cannot have defined Policies to be followed as these are not supported.

Ready to go next steps?

Icon for Product Regsitration - Layer2 leading solutions

Register for free download.

Keep your Sharepoint in sync. Download and try today.

Contact Us Icon for Layer2 leading solutions

Questions? Contact us.

We are here to help. Contact us and our consulting will be happy to answer your questions.