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

Investigate Issue with 'Write to Table' Access in Clay Workspace

·

·

https://app.clay.com/workspaces/33895/tables/t_EXNaXx7feDX3/views/gv_xQoS9gi2YjWy Can we have someone investigate why the 'write to table' is saying Not sure what has happened, but wont let us write to other tables?

Loading attachments

Investigate Issue with 'Write to Table' Access in Clay Workspace | Clay

10 comments

· Sorted by Oldest

Jamie M.
·
·
https://app.clay.com/workspaces/33895/workbooks/wb_3mwumiqJNeRU/all-tables here is the workbook structure if easier
Muhammad S.
·
·
here is the table: https://app.clay.com/workspaces/33895/tables/t_EXNaXx7feDX3/views/gv_xQoS9gi2YjWy
Jamie M.
·
·
Muhammad S. can you assist
Jamie M.
·
·
beat you to it Muhammad S.
Jamie M.
·
·
Loading attachments
😈1
Muhammad S.
·
·
hey Bo (. - I have replaced the HTTP api keys after the data has passed through initially. Right after I changed the HTTP API KEYS for XANO DB it started to throw this error in the write to other table column.
Muhammad S.
·
·
Changed API keys here: just FYI\
Loading attachments
Muhammad S.
·
·
Bo (. I did, it still contains the same error - I played around with it a bit and I think it is because of the chaining of multiple tables. We know the reason, but is there any way that you could make an exception for this specific scenario and let us work on the architecture we have created? In the worst case scenerio we have to rethink the whole design which will take us two weeks back. Thank you and would really appreciate your help.
Channeled
APP
·
·
We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!
Channeled
APP
·
·
Hi Jamie M.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: