Help Needed: Salesforce Created At Column Issue | Clay

Help Needed: Salesforce Created At Column Issue

Hey guys, can you help us with this? My Salesforce field was mapped with your "Created At" column. And since the beginning of the week, this column is considered as "deleted" as you can see on the first screenshot. On the second one, you can see that I can not find this column anymore even if I can display it on my table (screenshot 3) It's the same on each table

8 comments

Clay
APP
·
·
This issue might be related to how date fields are formatted between Clay and Salesforce. The "Created At" column may appear as deleted in Salesforce mapping because of formatting incompatibility. When integrating with CRMs like Salesforce, date format mismatches can cause fields to appear missing or deleted. You can still see the column in your table because Clay maintains it locally, but the integration may no longer recognize it. Try using the Format Date/Time formatter in Clay and select Unix Timestamp as your output format. Keep the column type as text rather than date format to avoid these compatibility issues.
Sources: Table columns | Documentation | Clay University Sources | Documentation | Clay University
Romain L.
·
·
still cant find the column to do a date/time formatting:
Andi D.
·
·
seeing same issues
1
Gabe E.
·
·
Hi there, sorry you had this issue here! I'm having trouble accessing the table link to best help here. Do you mind sending the link (url) to the table so we can take a look?
(52 kB)
Romain L.
·
·
hey Gabe E., sure: https://app.clay.com/workspaces/19532/workbooks/wb_0swpmhvqwbgsF4JNyFM/tables/t_0swpmipD2tFBNZEetHi/views/gv_0swpmiqxtUPosQ4gUGg every table are in this case FYI Thanks
Smit V.
·
·
Hi Romain, Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more! Let me know if I can help you with anything else :) - Smit
Bo (.
·
·
Good news! Happy to report that we heard back from the team and this issue should be fixed. Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble. Thank you for your patience as we worked on it.
🎉1
Romain L.
·
·
Hey guys! a huge thanks to all of you 🙂 Have a nice week