Airtable is doing that because your field content is spread across multiple lines. With the content on a single line, there’s no confusion (generally) about where it begins and ends. However, when the content of a single cell is spread on multiple lines, the extra surrounding quotes are added to clearly indicate that all the lines together are to be treated as a single entity from a single cell, not multiple cells. (My gut says that the duplicated inner quotes are also part of that mechanism, and I’ve got some thoughts about how the Airtable copy/paste system is treating them, but I won’t go that deep here.)
The bottom line is that I’m not aware of a way to tell Airtable to not do what it’s doing. I’ve run into this same issue, and have had to use the same workaround. In my case I only needed to copy from a single field, but I can definitely see how it’s a pain when copying from the same field across multiple records.
On the plus side, Airtable does not return all of those extra quotes to scripts. While not ideal, you could write a short manually-run script that will mash the content of all cells from a given field into a single string (separated by newlines) and display it in the output. Then you’re back to a single select-all operation to collect the data. Running the script is an extra step, but if you don’t need to run it often, it might be a tolerable step.
(whoops, missed the notification for this response last month)
In my case there are several hundred records parsed by the json constructor function, so manually copying it is more overhead than I’d like.
Yes, either this or minifying the json output (which would put it in a single line) should be a workaround. Will give it a shot. Not the ideal solution, but it would be better than what I have now (which is a collection of cases that replace quotes based on their position and preceding/following string in my destination as an awk/shell script).
IMO Airtable should have a clean() function that can be called in-formula like Excel to help mitigate these kinds of situations. If I paste the output into Excel as a string, and then apply clean() to those cells, the issue is corrected.
Not sure if I have to send this feedback somewhere else other than this forum post. Any idea @Justin_Barrett? Maybe here?
@Orun_Bhuiyan That category is one place to share feedback, but you can also write directly to firstname.lastname@example.org and share your thoughts. It’s anyone’s guess if a function similar to Excel’s clean() function will ever be added, but it couldn’t hurt to ask!