Issue with Dynamic List Name in SharePoint to Azure DataLake Synapse Pipeline

Sakshi Deshpande 20 Reputation points
2025-08-13T08:11:48.89+00:00

Hello,

I’m currently working on building a data pipeline to copy SharePoint Online list data into Azure DataLake. The pipeline uses a Lookup activity to retrieve the list names and a Copy activity within a ForEach loop to process each list.

The pipeline executes successfully when the list name is hardcoded. However, when I attempt to pass the list name dynamically, I encounter the following error:

Requesting response from path SharePointListExample and query $top=10 failed with status code NotFound and message: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"> <code></code> <message xml:lang="en-US">Resource not found for the segment 'SharePointListExample'.</message> </error>

It appears that the dynamic list name is not being resolved correctly in the request path. I would appreciate any guidance or suggestions on how to resolve this issue.

Thank you!

Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
{count} votes

Accepted answer
  1. Venkat Reddy Navari 5,815 Reputation points Microsoft External Staff Moderator
    2025-08-13T13:36:54.6+00:00

    Sakshi Deshpande the value SharePointListExample you see in the dataset dropdown is the internal API name the connector expects. If your Lookup is returning "SharePoint List Example" (with spaces), even URL-encoded, the connector won’t match it.

    Try having your Lookup return the internal name exactly as shown in the dropdown (SharePointListExample) and pass that directly to the dataset parameter (no encoding).

    Alternatively, you can pass the list GUID from SharePoint the connector can resolve that without worrying about spaces.

    Once the dynamic value matches the internal API name or GUID, the NotFound error should go away.


    I hope this information helps. Please do let us know if you have any further queries.

    Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.