Hello! Are there any limitations on how many lookup columns can be in one table? For some reason I can't get data from a third lookup column while first two are working just fine
Hi Alex, thanks for reaching out. You should not be running into issues after setting up just three lookup columns. Do you mind sending the link to the table so we can take a look?https://downloads.intercomcdn.com/i/o/1171717996/ac7729f84b426e1d0358af02/image.png?expires=1731596400&signature=69ad4da55b7a29272b55aff9ea0f1de671f9473e062d45705491f9eeb6a3bb0e&req=dSEgF85%2FmohWX%2FMW1HO4zYTywSr5D5ES2BKsam%2FhVPu8pQ%3D%3D%0A
Also, please help me with (probably) related question. I got stuck with making a lookup column if the previous lookup returned the expected result (in my case it's 'Contact Name') What should be the conditional for the lookup not to run?
If you're still experiencing this issue, can you kindly perform a hard refresh for me? This seems to be a temporary frontend issue, I'm able to link the lookup column in the prompt on my end. Here are some instructions on how to do it:LBKSMac: Chrome and/or Firefox = Press Cmd + Shift + RSafari = Press Cmd + Option + RPC:Chrome, Firefox, Microsoft Edge = Press Ctrl + F5
Let me know if this fixes the issue!
As for your second question on running columns conditionally, I recorded this quick video to show you how to set this up: https://www.loom.com/share/c5c18acf57594656a80c6167bf8e7b5a?sid=985e4404-8fc4-41fc-9263-6523efbf2a39
still same result. Can it be related to the Run conditional? I have run only: !_.some({{PPM Lookup}}?.records, 'Contact name')
Bruno, in your video the IT lookup column is also empty
Just to clarify, the issue is that you're not able to link specific outputs of your lookup columns in the GPT prompt?
It exists but UI shows that there is no data inside
Yes, I can't get to the response inside of the lookup. It doesn't show the array inside
I see what you mean now thanks for your patience Alex. Will take a closer look.
I followed the instructions from the video. It works with hthe first column (Change Lookup). But it does not work with the second lookup (IT Lookup) when the Change has a result 'Run condition not met'
Could you check if the issue still persists? I believe the lookup reference is now functioning as expected::LBKS[https:://downloads.intercomcdn.com/i/o/w28k1kwz/1251836056/13b78f39c302a5a9bb628b64bf74/CleanShot+2024-11-14+at+09_49_13%402x.png?expires=1731597300&signature=0f97791b7be36a7456063591c7f14312d72ff43e194d5bb445fa413923b10d6a&req=dSIiF8F9m4FaX%2FMW1HO4zWlugJgio5ePomIzD%2BJHakjw9bhOBL2wgrDRwn7Y%0A2g5n%0A](https://downloads.intercomcdn.com/i/o/w28k1kwz/1251836056/13b78f39c302a5a9bb628b64bf74/CleanShot+2024-11-14+at+09_49_13%402x.png?expires=1731597300&signature=0f97791b7be36a7456063591c7f14312d72ff43e194d5bb445fa413923b10d6a&req=dSIiF8F9m4FaX%2FMW1HO4zWlugJgio5ePomIzD%2BJHakjw9bhOBL2wgrDRwn7Y%0A2g5n%0A)
The third lookup works as expected when Change has a response (even if it's no record found) But it runs when Change has 'Run condition not met' as a response
And I want it not to run
Believe it or not:
BTW, the same situation in formula builder:
Bruno, I don't understand why but it is the related to conditional run in IT Lookup. I removed the conditional and it runs perfectly from prompt
Bruno, I fixed it with changing the conditional run criteria
Or maybe you fixed it on your end )))
A temporary solution would be to run the column without the run conditions for now. I’ve flagged this issue to our engineering team to investigate how we’re querying record results—something definitely seems off here. Thanks for catching this! We’ll keep you updated as soon as we have more information.
Bruno, is there a workaround for this? I understand that I can't get the data from this lookup in formulas or prompts. Is there a way to extract that data as JSON array to another column and use this column in promts?
Here's what you can do: remove the run conditions for that column, and you should be able to pull the records from the lookup. However, keep in mind that this might clutter your prompt if you're adding all these elements to the context window. A better workaround might be to specify this directly in the prompt, such as instructing it to check one source and, if empty, check another. This approach could help streamline things.