.png){kind=logo}
Error with Lookup Multiple Rows Column Despite Correct Parameters
I'm encountering an error with the Lookup Multiple Rows column, it returns error even when the right parameters are set.
Jim O.··
I apologize for the inconvenience you're experiencing. The Lookup Multiple Rows feature is designed to search and retrieve data from other tables in your workspace. It requires specific inputs: 1. Table to Search 2. Target Column 3. Filter Operator 4. Row Value 5. Limit (Optional) If you're encountering an error despite setting these parameters correctly, it might be due to a technical issue. To troubleshoot: 1. Double-check all input fields 2. Ensure the target column exists in the table you're searching 3. Verify the filter operator is compatible with your data type If the problem persists, you may need further assistance. Please request human support by clicking on "Talk to a person" for a more in-depth investigation of your specific setup.
If your Lookup Multiple Rows column is returning an error despite correct parameters, there might be a processing issue. To resolve this: 1. Delete the affected column 2. Create a fresh column 3. Re-map your data to the lookup multiple rows action Make sure you've set all required inputs: ** Table to Search ** Target Column ** Filter Operator ** Row Value * Limit (Optional) If the problem persists after these steps, it may require further investigation. In that case, please request human assistance by clicking on "Talk to a person" for a more in-depth look at your specific setup.
what api are you using?
Bo (.··Jim - Do you mind sending the link (url) to the table so we can take a look?
(52 kB)
- Jim O.··
here
- Bo (.··
Hey, sounds like the issue might be with your API connection. It looks like your API account was deleted. Here’s how to fix it: 1. Go to Settings > Account > API Key and copy your key. 2. Then go to Connections, search for Clay, delete the existing connection, and add a new one using your API key. 3. Head back to your Lookup Multiple Rows column, re-save it with the new connection, and run it again. That should clear the error—let me know how it goes!
- Jim O.··
we did not delete it, the Clay API key is still there
- Bo (.··
Got it—thanks for the screenshot but it doesn’t seem to be working properly. Normally, when the connection is active, you’d be able to see the table names when selecting a table to look up into. Right now, nothing’s showing up, which suggests the connection isn’t fully recognized. To fix it, try removing the current API connection and re-adding it. That usually resets the connection and gets things working again. Let me know how it goes!
- Jim O.··
I redo the connection and it worked. Thanks!