Home
Events
Groups
Members

00 Clay Announcements
01 Community General
01 Props and Wins
01 Watercooler
01 Welcome and Intros
02 Bugs
02 Starting with Clay
02 Support
03 Feedback & Requests
03 Tutorials & Inspiration
04 FT Job Opps
Gtm Career Advice
Member Spotlight

Community Guidelines

Powered by Tightknit

Issue with Table Selections Not Functioning in Clay App | Clay

Issue with Table Selections Not Functioning in Clay App

Andrei Baloleanu (Adyntel)

·

·

Are you having a bug? This was working great until 15 minutes when I starting getting this in multiple tables like this one. As you can see in the setup there, I had all those fields available to select to write in another column but now it doesn’t allow me to select anything from that timetable…

Loading attachments

4 comments

· Sorted by Oldest

Channeled
APP
·
·
This sounds like a front-end performance issue. Try clearing your cache and refreshing your screen to see if the field selection functionality returns. If the issue persists after clearing cache and refreshing, please request human assistance by clicking on "Talk to a person" so our team can investigate this specific bug with your table setup.
Clay
APP
·
·
Hello Andrei! Thanks for reaching out! I can see you are able to now select the columns you want to send to the other table. You have not selected however columns to map them to in the destination table or simply create a new column.
(1623 kB)
Let me know if I have misunderstood the issue or it is not persistent anymore. Thanks!
Andrei Baloleanu (Adyntel)
·
·
The problem was at the last ones where it wasn’t recognising the columns from “timetable”. Look at the printscreen I sent to see exactly what I’m talking about and the fact that timetable is not recognised as a list anymore
Clay
APP
·
·
Hey Andrei! I checked with the team and tried doing a Send Table Data and sending data at different depths (nested fields). Looks like beyond Timetable the table is not able to send the data. Looks like a limitation to me.
I am in touch with the team to see if there is a possible workaround for this!