Hi @Sai Kiran
Thank you for the clarification and for providing the details about the column type being a 'Lookup' field in the SharePoint Online List.
In Azure Data Factory, when using the SharePoint Online List connector, there are certain column types that might not be ingested correctly, including 'Lookup' fields. These fields often reference other lists or external data, which can sometimes cause issues during ingestion. The default behavior might not handle these references as expected.
To resolve this issue, I recommend the following:
- Check Data Preview and Mapping: Double-check the data preview and ensure that the 'Lookup' column is mapped properly in the dataset. You may need to adjust the column mapping to ensure the correct handling of Lookup data.
- Use a Custom Query: If possible, try using a custom query or a filter that explicitly includes the Lookup column. This may help ensure it gets picked up in the data pipeline.
- Flatten Lookup Columns (Optional): If the Lookup column points to another SharePoint list, consider flattening the data by expanding the related information (such as ID or Value fields) from the lookup list. You can achieve this by joining the lists in your query or using additional transformations within Azure Data Factory.
- Check SharePoint API Limitations: Ensure that there are no limitations or restrictions on the SharePoint API side when querying Lookup columns, as certain configurations can affect their accessibility.
If these steps don’t resolve the issue, it could be beneficial to explore using a different connector or method, such as using the SharePoint REST API or Power Automate, depending on your requirements.
I hope this helps! Let me know if you have any further questions or concerns.