Issue with checkbox columns - whereby the checkbox is neither True or False, it is just kind of greying out... Video: https://www.loom.com/share/0c9a897b985b4e9c808e86718a162e62?sid=3569410b-92f1-4abc-b89c-18afbe416ac8
The checkbox column in Clay is designed to be a true/false field that displays a checkbox. It's typically used for conditional runs and should show either a checked (true) or unchecked (false) state. If you're seeing a greyed-out checkbox instead of a clear true or false state, this could indicate a potential issue with the data in that column or how it's being processed. It's possible that the column is receiving data that doesn't conform to the expected true/false format. To troubleshoot this, you might want to check the following: 1. Ensure the column is set to the correct data type (Checkbox). 2. Verify the data being input into this column is in the correct format. 3. Try clearing and re-entering the data in a few cells to see if it resolves the issue. Can you provide more details about how you're populating this checkbox column? Are you using a formula, importing data, or manually entering values?
The checkbox column in Clay is designed to be a true/false field that displays a checked (true) or unchecked (false) state. If you're seeing a greyed-out checkbox, it might indicate an issue with the data type or the data itself. To fix this: 1. Verify the column's data type: • Right-click the column • Select "Edit Column" > "Select Data Type" • Choose "Checkbox" as the data type • Click "Save Settings" 2. If the issue persists, try these steps: • Delete the affected column • Create a fresh checkbox column • Re-map your data If you need further assistance, please request human help by clicking on "Talk to a person".
Hi Daniel, thank you for reaching out! I apologize for the inconvenience, I understand how frustrating this can be. It does seem like an unusual problem. I tried duplicating the formula column on my end, and the new column works as expected without the issue you described. I recommend deleting the old column, keeping the new one, and using it as the condition for your workflow going forward. I hope this helps! If you have any other questions or need further assistance, please let me know :) – Smit
Happy to help :)
I'll tentatively mark this closed for the moment, but keep in touch if you hit other roadblocks.
Smit V. it has come back to rear it's ugly head just now! https://app.clay.com/workspaces/273614/workbooks/wb_KDYnQqhurF9B/tables/t_9JDMNqZ9XePU/views/gv_DdYJZJDRVzmN All good for hundreds/thousands of records then starts happening again near the bottom there...
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
I've escalated this to our engineering team, and they're currently investigating the issue. I'll update you as soon as I have more information. In the meantime, could you please keep a few of those glitchy cells unchanged? This will help our engineers identify what's causing the problem. Thank you for your patience!
Yep will keep them there glitched no probs - they're mostly towards the bottom of this table
Thank you!
yes still waiting to hear back...
Hi Daniel, I recommend duplicating the formula column and continuing with your workflow, while keeping the glitched column as is for the engineers to review. This way, your process won’t be interrupted while we work on a fix. Thanks!
Will do 👍 - challenging one huh!?
It kinda is, we are not seeing this for other people and unable to replicate as well so seems one off. Thank you for being understanding!
Hi Daniel, no news as of now. I’ve heard back from our engineering team and can confirm that we’re adding this issue to our backlog. For greater context, our product team prioritizes bugs based on the severity of the issue and how widespread of an experience it is with customers. To set expectations, items like this may not be addressed for some time. The timeline is based on the team's current existing set of work and upcoming feature releases, all subject to change. So what happens now? Now that your issue has been logged, I will tentatively mark this as closed. Please note that I will reach out to you as soon as I receive any new information about this bug. If you don’t hear from me, then the engineering team is still working on it. As soon as there's an update, this conversation will automatically re-open on my end and I will follow up with you. Do you have any further questions before I step away from this conversation until I have an update for you?
.png){kind=logo}
