How to Fix SharePoint Lookup Columns Not Updating from Databricks
Question details
Users are unable to successfully update SharePoint lookup columns via Databricks integrations, even though standard text and number fields update correctly.

- Product
- SharePoint, Databricks
- Device & OS
- not provided
- Scenario
- Sending data from Databricks to update a SharePoint list using an integration tool like Power Automate, Power Apps, or Microsoft Graph.
- Observed behavior
- Standard fields are successfully populated with Databricks data, but lookup columns remain unchanged or throw an error because the connector is receiving display text instead of the required SharePoint lookup ID.
Confirm whether your environment is using SharePoint Online or SharePoint Server, and ensure you have administrative access to review the connector configurations (such as Power Automate or Microsoft Graph).
Pass the SharePoint Item ID Instead of Display Text
Configure your integration connector to send the unique integer ID of the lookup item rather than its plain text value.
When integrating Databricks with SharePoint, relational fields like lookup columns cannot process raw text strings. The SharePoint REST API and connectors like Power Automate require the explicit integer ID from the source list to map the relationship correctly.
Determine if your Databricks pipeline is sending data to SharePoint via Power Automate, Power Apps, Microsoft Graph API, or a custom third-party connector.
Navigate to the source SharePoint list that your lookup column references. Modify the list view to display the 'ID' column so you can see the integer values tied to your data.
Open your connector configuration (e.g., the 'Update item' action in Power Automate). Locate the field for your lookup column.
Adjust the incoming data mapping from Databricks so that the payload specifically passes the target 'ID' (e.g., passing the number '15' instead of the text 'Completed'). For REST API calls, append 'Id' to the internal field name (e.g., 'CategoryLookupId').
Run a test execution of your pipeline. Review the run history or error response logs to confirm the lookup column updates successfully without 'invalid lookup value' errors.

Experience Seamless Document Management with WPS Office
While resolving complex list integrations and backend connector issues in SharePoint requires technical configuration, managing your actual office documents should be straightforward. WPS Office is a lightweight, free alternative that offers comprehensive tools for your daily document needs without the steep learning curve.
- 1. Download the Installer: Visit the official WPS Office website and download the free installer for your operating system.
- 2. Install the Software: Run the setup file and follow the quick on-screen instructions to install WPS Office on your device.
- 3. Start Creating: Launch WPS Office and immediately open or create Writer, Spreadsheet, or Presentation files with high compatibility.

Frequently Asked Questions
Why do standard SharePoint fields update successfully while lookup columns fail?
Standard text and number fields accept flat data directly from Databricks. Lookup columns, however, are relational and require the unique integer ID from the referenced SharePoint list to establish the link. Providing just the display text causes the update to fail.
How do I find the correct Item ID for a SharePoint lookup column?
You can find the Item ID by going to the source SharePoint list that the lookup column pulls from. Edit the current list view to make the 'ID' column visible, which will display the unique integer for each item.
How do I map a lookup field ID correctly in Power Automate?
In your 'Create item' or 'Update item' action, click on the dropdown for the lookup column and select 'Enter custom value' at the bottom of the list. Then, map the dynamic content containing the integer ID from your previous steps or Databricks payload.
Can I update multiple lookup values at once?
Yes, but updating a multi-select lookup column requires passing an array of objects containing the IDs. The exact JSON array format depends on whether you are using the Microsoft Graph API or the SharePoint REST API.




