Forum Discussion

schneiw's avatar
schneiw
Advocate IV
4 months ago
Solved

Data Pipeline reading from Sharepoint List

as anyone been able to get the Copy Data activity to work for reading data from a Shrepoint list? I insert the Connections but it fails to test with this message. I use the same Connection succesfully however in a DataFlow Gen2, so it cant be that?

 

Failed to get metadata of odata service, please check if service url and credential is correct and your application has permission to the resource. Expected status code: 200, actual status code: Conflict, response is : <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>Request Error</title> <style>BODY { color: #000000; background-color: white; font-family: Verdana; margin-left: 0px; margin-top: 0px; } #content { margin-left: 30px; font-size: .70em; padding-bottom: 2em; } A:link { color: #336699; font-weight: bold; text-decoration: underline; } A:visited { color: #6699cc; font-weight: bold; text-decoration: underline; } A:active { color: #336699; font-weight: bold; text-decoration: underline; } .heading1 { background-color: #003366; border-bottom: #336699 6px solid; color: #ffffff; font-family: Tahoma; font-size: 26px; font-weight: normal;margin: 0em 0em 10px -20px; padding-bottom: 8px; padding-left: 30px;padding-top: 16px;} pre { font-size:small; background-color: #e5e5cc; padding: 5px; font-family: Courier New; margin-top: 0px; border: 1px #f0f0e0 solid; white-space: pre-wrap; white-space: -pre-wrap; word-wrap: break-word; } table { border-collapse: collapse; border-spacing: 0px; font-family: Verdana;} table th { border-right: 2px white solid; border-bottom: 2px white solid; font-weight: bold; background-color: #cecf9c;} table td { border-right: 2px white solid; border-bottom: 2px white solid; background-color: #e5e5cc;}</style> </head> <body> <div id="content"> <p class="heading1">Request Error</p> <p>The server encountered an error processing the request. See server logs for more details.</p> </div> </body> </html>.

 

  • Hi schneiw,

    Thank you for reaching out to the Fabric Community. I’m happy to assist you with your query.

     

    • Based on your description, you are encountering this error while reading data from a SharePoint Online List using the connector. Could you please confirm whether you are implementing this in an Azure Data Factory (ADF) pipeline or a Fabric pipeline?
    • If you are using a Fabric pipeline, this scenario typically works without issues. I recommend performing the validation steps outlined below. Please let us know if you continue to face any challenges.

    1) Craete pipeline and open the below option to copy activity.

     

    2) After adding copy data activity  then click source and broswe for the source.

    3) Now select the relevant sharepoint source from the options listed.

     

     

    4) It will open the below prompt and ask to login with your account. Do, so and connection will be craeted.

     

    E.g Site URL: https://orgname-my.sharepoint.com/personal/[email protected]     

     

    5) After the successfull connection you can perform copy activity task on the file you want.

     

    If you find this response helpful, kindly consider marking it as the accepted solution and giving it a kudos. This helps others facing similar issues and is greatly appreciated.

5 Replies

  • Hola  schneiw ,

     

    Este error en SharePoint puede resultar bastante engañoso, ya que parece un problema de credenciales o de Fabric, pero en la mayoría de los casos no lo es.

     

    Comenzaría por comprobar dos cosas básicas:

    1. Prueba el endpoint directamente en un navegador o Postman agregando /$metadata.
      Si devuelve HTML en lugar de XML, el problema no está en Fabric, sino en el propio servicio.
    2. Asegúrese de que la URL utilizada sea la URL del sitio de SharePoint , no la URL de una lista o carpeta.
      Es muy común copiar la URL directamente desde la interfaz de usuario (por ejemplo, una biblioteca de documentos o una lista), lo que genera un punto final OData no válido.

    Si estas comprobaciones son correctas y el problema solo se produce en un sitio o lista específicos, generalmente está relacionado con la configuración de SharePoint. Existen casos conocidos en los que los tipos de columna complejos (metadatos administrados, búsquedas de valores múltiples, campos de selección múltiple de personas, etc.) impiden que el punto final OData genere metadatos válidos y provocan un error 409. (Consulte esta publicación:  https://community.fabric.microsoft.com/t5/Copy-job/OData-Error-When-Connecting-to-SharePoint-Online/mp/5131842 )

     

    Como paso de validación rápido, intente conectarse a una lista simple recién creada en el mismo sitio. Si funciona, es probable que el problema esté relacionado con el esquema de la lista original.

     

    Dado que trabajas con SharePoint, te recomiendo que pruebes un acceso directo de SharePoint en Fabric ( https://learn.microsoft.com/en-us/fabric/onelake/create-onedrive-sharepoint-shortcut . En muchos casos, este método es más sencillo, ya que permite acceder a los datos directamente sin canalizaciones ni transferencia de datos, evitando así la dependencia del punto final OData.

    En resumen, yo revisaría:

    • URL correcta (a nivel de sitio)
    • Respuesta de/$metadata
    • Esquema de lista (tipos de columna)
    • Ya sea que el problema se limite a un sitio o lista específicos

    En la mayoría de los casos, la causa principal es una URL incorrecta o limitaciones del punto final OData de SharePoint, en lugar de un problema de Fabric.

     

     Si mi comentario te ayudó a resolver tu pregunta , te agradecería que lo marcaras como la solución aceptada and give me like. Esto ayuda a otros usuarios con el mismo problema y me motiva a seguir contribuyendo.

    Muchas gracias. 

  • v-prasare's avatar
    v-prasare
    Community Support

    Hi schneiw 

    if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.

     

     

     

    Thank you for your patience and look forward to hearing from you.
    Best Regards,
    Prashanth Are
    MS Fabric community support

  • Hi schneiw,

    Thank you for reaching out to the Fabric Community. I’m happy to assist you with your query.

     

    • Based on your description, you are encountering this error while reading data from a SharePoint Online List using the connector. Could you please confirm whether you are implementing this in an Azure Data Factory (ADF) pipeline or a Fabric pipeline?
    • If you are using a Fabric pipeline, this scenario typically works without issues. I recommend performing the validation steps outlined below. Please let us know if you continue to face any challenges.

    1) Craete pipeline and open the below option to copy activity.

     

    2) After adding copy data activity  then click source and broswe for the source.

    3) Now select the relevant sharepoint source from the options listed.

     

     

    4) It will open the below prompt and ask to login with your account. Do, so and connection will be craeted.

     

    E.g Site URL: https://orgname-my.sharepoint.com/personal/[email protected]     

     

    5) After the successfull connection you can perform copy activity task on the file you want.

     

    If you find this response helpful, kindly consider marking it as the accepted solution and giving it a kudos. This helps others facing similar issues and is greatly appreciated.

    • Lodha_Jaydeep's avatar
      Lodha_Jaydeep
      Solution Sage

      Hi schneiw,

       

      I hope your issue has been resolved. If you are still encountering any errors, please feel free to reach out to the community for further assistance.

      If the steps I provided were helpful, kindly consider marking the response as the accepted solution and giving it a kudos.

      This helps others facing similar issues and is greatly appreciated.

  • Thank you all, it appears it was just my URL in the connection that was not correct. I had reused the connection from the Copy Job, that sems to be a mistake, not sure why they are different, but the trick was to create the connection via the data pipeline UI to get the valid URL crqted correctly.