.png&w=3840&q=75){kind=logo}
Table Filter Option Not Working - Please Investigate
Hello Team, the filter option is not working for this table. https://app.clay.com/workspaces/257306/tables/t_AYXEC5rsxbn2/views/gv_FcpdwDZRbKym Could you please look into this?
Hello Team, the filter option is not working for this table. https://app.clay.com/workspaces/257306/tables/t_AYXEC5rsxbn2/views/gv_FcpdwDZRbKym Could you please look into this?
👋 Hey there! Our support team has got your message - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in this thread so that we can help you as quickly as possible!
Filter is not working for any of these columns.
Hey there, thanks for reaching out! Looks like you're trying to filter out those rows which do not contain "@" here. The filter seems to be working as expected. I created this duplicate view to show you all the cells which do not contain "@", it looks like they are simply empty cells. for which none of the providers you set up returned email data. Can you clarify which aspect of this filtering behavior is confusing or incorrect for you?
I was first trying "not empty".
I did not work and then I had to figure out another way.
Hey there, thanks for clarifying what's causing issues here! It looks like we've got a bug on our hands - I've escalated this over to our engineering team and we'll let you know as soon as we know more. In the meantime, filtering the column by verifying whether specific identifiers, such as "@" are present in individual cells will be a good way to temporarily work around this issue.
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 provide insight on expectations, issues like this may not be actioned for some weeks. This timeline is based on the team's current existing log of issues and upcoming feature releases which is subject to change. So what happens now? Now that your issue has been logged, I will wrap up this conversation. 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?
Good news! Happy to report that we heard back from the team and this issue should be fixed. Thank you for your patience as we worked on it. Please let us know if the problem has been resolved on your end, or if you still have trouble.
