Why is this "Failed to parse formula for "columnValuesToColumnMappings->..." happening in this Write to Other Table? Failed to parse formula for "columnValuesToColumnMappings->f_3pxMqmRV4HXE" with error: {"offset":35,"token":{"value":"o"}} Failed to parse formula for "columnValuesToColumnMappings->f_PCD5fDoR4ylS" with error: {"offset":35,"token":{"value":"o"}}
I don't have a list to send so that field is blank and that's never been a problem.
AFAIK, I dont think any of the destination columns have been repeated.
Based on your description of the error occurring with a blank list field, here's what might be happening:For column mapping in Write to Table, you need to:1. Enter "/" in the list selection step to explicitly skip list mapping when you're not working with lists 2. Then properly map your source columns to destination columnsThe error suggests there might be an issue with how the column mappings are configured. Double-check that:** All the columns you're mapping to actually exist in the destination table ** The column names match exactly * The data types between source and destination columns are compatibleIf you continue experiencing issues after verifying these points, you may want to try reconfiguring the Write to Table integration from scratch to ensure there are no misconfigurations. Source: Write to table integration overview | Documentation | Clay University
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Okay - identified the problem. WriteToTable doesn't read / write columns with double quotes (") in their name.
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!
Hey there - just wanted to check in here to see if you needed anything else! Feel free to reply back here if you do.
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!
Hi Siddhant B.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: