Link to other base


#339

@Katherine_Duh There is a straight-forward common thread in all the use cases. The vast majority of use cases I’m reading here have to do with data normalization and reuse of functionality. People don’t want to duplicate the same data and features across different bases.

It’s pretty simple, IMO:

  • If I have a list of people, I don’t want to recreate my CRM functionality across multiple bases and have duplication.
  • If I have a list of products, I don’t want to recreate my entire product-catalog functionality across multiple bases and have duplication.

Most relational databases allow you to link across databases, and some even allow you to link across database servers. This may be restricted to virtual views, read-only access, or whatever. But it is an essential feature when working with complex database, which I’m sure most of your customers evolve into over time.

I haven’t read every post here, but reading several of the recent posts, it seems like an update on your considerations and status on this would be greatly appreciated.


#340

I thought that this idea was so self explanatory that I submitted a support request thinking I was too dumb to find the feature. I second this request.


#341

+1 from here - need this so badly.


#342

Waiting for this feature


#343

@Katherine_Duh - having thought about this for a couple of days, the most elegant solution in my mind would be the ability to “import a view” of a table from one base to another.

If I’m in Base A, I could have a table from Base B represented in A as a read-only, dynamically-updating view. I could then use those records in Base A. Users in Base A would have read-only view access to that table.

Then you could have a feature that shows where else a table is being used, e.g., the Base B team can see that one of their tables has been imported to 3 other Bases, and be in touch with those teams if they’re making a schema change, for instance.


#345

+1

When was the last time someone from @Airtable addressed this question?
I tried reaching out on Twitter but didn’t receive a reply.


#346

+1 As @Javid_Jamae said, the ability to NOT recreate the same data across different bases (products, for example).


#347

I am sure Airtable does understand the importance of this feature but they are not able to figure out the right solution I guess.


#348

+1 for solutions that allow data to be shared between bases. Our use cases are similar to others described above. For example, we would like to start a secondary base for a social media intern to draft posts and we would like the secondary base to pull some data (social handles but not sensitive info) from the CRM in our primary base. Ideally, the intern would have the ability to update those social handles, pushing the change back to the CRM, although that’s not the priority. Having the data flow from our CRM to the Intern’s base is the more important priority. We’re excited to see if this is something that can happen someday in Airtable. Thanks.


#349

So we can’t link databases as of now? How about linking information from columns?


#350

I think this would be a MAJOR win for Airtable users. Please consider it!!


#351

This is the most significant missing feature I’ve noticed since I started using Airtable recently.


#352

Please add this feature, major hassle at the moment…


#353

This feature will unlock so much potential for me and my team.
Actually, the main reason a part of my team considers moving to Monday,
is because of the clutter we’ll have if we decide to manage all our projects on one base (with all of the other tables).


#354

I’ve been on and off thinking that I can use Airtable for the last 7 months to replace my existing solution. This is yet another feature than pains me.

Base cross linking lets me keep my static info(admin base) protected from the data entry base(used by everyone). Additionally, this would help greatly with managing the number of tables in a single base, its a bit tedious scrolling through all my many tables.


#355

Any updates on this? Does airtable have a timeline for implementation? This would be a huge benefit…


#356

+1 We are new to Airtable and this was one of the first pieces of functionality we were looking for.


#357

Crucial feature. Please implement.


#358

@Airtable_Support @Katherine_Duh It would be nice to have an update on this. This feature is really holding back what I would like to do in my business. I don’t want every single one of my airtable users to have access to my main base. It would be amazing to have linking between bases to restrict what a user can see of the primary base by linking to a more limited base.

Also, I don’t want one base to be source of every type of data (revenue vs inventory on product vs KPIs). It’s not relevant for my staff to have access to all of it.


#359

A web based “database” that can’t even link to itself?! This is a joke, surely?!

I don’t know where to begin. I’ve been waiting years to get rid of our collection of excel spreadsheets and link them into our SQL database. I’ve spent months waiting to move to AirTable - and sat down sketch in hand to start… and within 3 minutes (literally!) started trying to link two bases…

My use case:

  • I want a CRM of companies & contacts (similar to your CRM - which was my base)
  • I want a collection of details about actual customers for management

These share:

  • Offices/products - I want/need a single list of
  • Companies - I want the companies I speak to to end up in offices. I want their phone number, email, LinkedIn profile etc etc to be the same - not have the same data in two places

I just want to have look-ups that source data from another table. The permissions in my case is implicit - if I’m letting you pick a look-up you can see the items in it. If you click on it - you can only see what your permissions allow (which may be nothing - and it may then be just text)

I do not want a base that contains all of my sales data and another, island of data with all my actual customers in!

Why even offer multiple bases if they can’t work together! The relational database was designed in 1970 - that’s nearly 50 years ago!!!