Job Categorization Issues: Data Visibility and Decision Makers Formula | Clay

Job Categorization Issues: Data Visibility and Decision Makers Formula

"Job categorization" is a text column that should be the same for the entire column. Decision makers is a formula to pick the job titles related to the "job category" from the "Job categorization" column. I'll use that to search for job titles in that company. However, I see the Job categorization, for some reason, cut to the 23rd row, and it didn't output job titles in the "decision makers" column. But it still was searching for people. Is it just visually not showing the data, or is it empty, and it searches for anybody from the company? Here's a video to understand it better: https://www.loom.com/share/6d2f88d372814dada28afa41682b3399?sid=95ccb147-56b0-458c-b794-6cc2685edca5

6 comments

Alexander T.
·
·
https://app.clay.com/workspaces/258754/workbooks/wb_rKb4cgAfQP2J/tables/t_GakErMQGnNWW/views/gv_5cTzdhEw7gy8
Bo (.
·
·
Hi there, Thanks for reaching out. The reason you’re seeing this issue is that text columns in Clay are treated like formula columns. If there’s no specific condition set, they won’t populate data in every row. To fix this, try the following: 1. Click on the ⚙️ icon for the Job categorization column. 2. Select Formula > Use AI. 3. Set up a condition, for example: If /column isn't empty, return "text". This should ensure data fills consistently across rows. Let me know if you have more questions!
Alexander T.
·
·
Yes, this doesn't solve my main issue which is that the JSON text column stops at the 23rd row. Why did that happen?
Bo (.
·
·
Hello, The reason the JSON text column stops at the 23rd row is due to the underlying formula. The text isn’t straightforward text but rather a formula that requires specific conditions. Since the formula in this column is designed to handle individual entries and not the entire column automatically, it will only populate rows where the condition (like a non-empty Company URL) is met. To fix this, I added logic that checks if Company URL has a value ({{Company URL}}?). This setup only outputs text when Company URL is populated, which allowed for partial functionality but required the use of two columns to avoid breaking the JSON structure. This workaround helps manage the logic without overloading or breaking JSON compatibility. If you need further assistance with this setup, feel free to reach out.
Alexander T.
·
·
Thank you so much < 3
Channeled
APP
·
·
Hi Alexander T.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: