Great video! What happens to the name record if that employee is no longer active? I don’t want be left with a blank record and also don’t want to sync the active and inactive employees for everyone to see.
You can simply create a view to filter out the records with the inactive employee, that way you don’t lose the record and it doesn’t go blank, hope that makes sense, thanks for watching! 🙏🏻
Is this also possible just for tables in one Base? For example if i am adding new records in Table2 than I want exactly the same records in Table1. Is this possible?
Yes, however copying the same data to another table is a bit redundant but it can be done through an automation. You'll have to add an automation where the trigger is any time a new record gets added to Table2, it adds the same record to Table1. The free plan only allows up to 100 automations per month and the team plan allows up to 25,000 automations per month. So it'll depend on how much data you are working with. There's a few things you'll need to setup in the target table to make this work correctly but it'll make my comment reply way too long to explain :)
Hi, I've made an automation to create a record with conditions from a sync base, because it was creating one record per collum :disappointed_face: So the first problem is solved, but now i need this record to be updated as long as someone change any info in the row of other table/base... Could you help me ? Thanks.
This will be hard to troubleshoot without seeing the entire setup, I’m a bit confused. Are the bases synced? Or is it an entirely different independent table you’re updating? It’ll be difficult to suggest anything without understanding the use case in detail…
@@LessonsUnlocked I have 2 bases synced, and the view works pretty fine, i've made an automation to create a kanban task in a "to do status" with the entire row of the record applying conditions of fullfing 2 cells. It works... the matter is: When someone change an info cell in the primary base the synced table works but the record created by the automation does not update :(
Sounds like you're making updates directly to the target synced table? If so, it is best practice to not touch the synced data but to pull and link another table to it with the fields you only need along with any other data you're adding. For example, if I'm syncing customer data I'll have a source and target table for that, but in the target base I'll add another table called Tasks to link to the customer data and only link or lookup fields I only need for the purpose of managing tasks. Avoid mixing sync data with custom data in the same table. I hope that helps as its always hard to suggest something without sitting down and looking at the setup in detail...
@@LessonsUnlocked actually i'm updating the original table from the other base but your suggestion to make another table to link will work fine, i'm doing it. mMany thanks.
Thanks a lot, it's crisp and clear
Appreciate you watching! 🙏🏻
Great tutorial. Short and sweet
Thank you 🙏 I try my best to keep it simple, succinct yet comprehensive, appreciate you watching!
I wonder if base can be synced with our Active Directory
Great video! What happens to the name record if that employee is no longer active? I don’t want be left with a blank record and also don’t want to sync the active and inactive employees for everyone to see.
You can simply create a view to filter out the records with the inactive employee, that way you don’t lose the record and it doesn’t go blank, hope that makes sense, thanks for watching! 🙏🏻
curious... any way to have a bi-directional sync? Possibly with pro-plan?
Yes, unfortunately not included in the free plan but in the business plan for two-way sync or multi-source syncing
Is this also possible just for tables in one Base? For example if i am adding new records in Table2 than I want exactly the same records in Table1. Is this possible?
Yes, however copying the same data to another table is a bit redundant but it can be done through an automation. You'll have to add an automation where the trigger is any time a new record gets added to Table2, it adds the same record to Table1. The free plan only allows up to 100 automations per month and the team plan allows up to 25,000 automations per month. So it'll depend on how much data you are working with. There's a few things you'll need to setup in the target table to make this work correctly but it'll make my comment reply way too long to explain :)
Hi, I've made an automation to create a record with conditions from a sync base, because it was creating one record per collum :disappointed_face:
So the first problem is solved, but now i need this record to be updated as long as someone change any info in the row of other table/base...
Could you help me ?
Thanks.
This will be hard to troubleshoot without seeing the entire setup, I’m a bit confused. Are the bases synced? Or is it an entirely different independent table you’re updating? It’ll be difficult to suggest anything without understanding the use case in detail…
@@LessonsUnlocked I have 2 bases synced, and the view works pretty fine, i've made an automation to create a kanban task in a "to do status" with the entire row of the record applying conditions of fullfing 2 cells. It works... the matter is: When someone change an info cell in the primary base the synced table works but the record created by the automation does not update :(
Sounds like you're making updates directly to the target synced table? If so, it is best practice to not touch the synced data but to pull and link another table to it with the fields you only need along with any other data you're adding. For example, if I'm syncing customer data I'll have a source and target table for that, but in the target base I'll add another table called Tasks to link to the customer data and only link or lookup fields I only need for the purpose of managing tasks. Avoid mixing sync data with custom data in the same table. I hope that helps as its always hard to suggest something without sitting down and looking at the setup in detail...
@@LessonsUnlocked actually i'm updating the original table from the other base but your suggestion to make another table to link will work fine, i'm doing it.
mMany thanks.