Retrieve linked record without coding secondary table name?

[Andrew_Hildebra]

I’m using the curl API to pull json data from a table linking to records in a secondary table.

I have a working function that pulls down and parses both tables. It then uses the record ID listed in the main table and plugs in the corresponding data in the secondary table. It works fine.

But it would be very helpful to perform this without coding the name of the secondary table. Is there any way to retrieve the name of the table source of the linked record without knowing it ahead of time? Or retrieve the record with just the ID and not the table name?

[pmsoltani]

@Bill.French How can we involve an Airtable staff in this conversation?

[Bill_French]

pmsoltani:

How can we involve an Airtable staff in this conversation?

To be clear - there are two completely unique feature issues in this thread. I’m referring to the latter (i.e., …the name of the table should be included in the API result.)

Airtable engineers and support people are watching this community very closely. I can’t speak for the team, but I imagine that sometimes they don’t actively respond into requests for new features because no one ever likes to say “no”. :winking_face: And there are plenty of feature requests that should never be developed (if ya’ know what I mean).

This one happens to be pretty good idea and would serve many needs. However, it is also an extended functionality that no one is truly denied from having. As I mentioned, I enhance my API result sets using the simple power of JSON serialization. It’s just so damned easy to create extensible features to the API. And for this reason alone, Airtable’s time is perhaps better spent improving aspects of the platform that cannot be extended so easily.

And you can also file a support request to voice the need, eh?

[pmsoltani]

This one happens to be pretty good idea and would serve many needs. However, it is also an extended functionality that no one is truly denied from having. As I mentioned, I enhance my API result sets using the simple power of JSON serialization. It’s just so damned easy to create extensible features to the API. And for this reason alone, Airtable’s time is perhaps better spent improving aspects of the platform that cannot be extended so easily.

Is this via the Google Apps Script that you mentioned earlier? If so, would you please provide an example on how to add the table name to the API result? Unfortunately, I’m not familiar with Google Apps Script and would appreciate the help.

And you can also file a support request to voice the need, eh?

Perhaps I will. Right now, I’m deciding on the architecture of my app, so I could be settling on a workaround for the time being.