Excellent, tutorial. Thanks! I have 2 questions, if I may. 1. Is it best practice to name the linked field something different than the name of the original field? Why or why not? 2. After creating a linked field with a look-up should I hide the look-up field til I need it so the table doesn't become too cluttered?
Thank you & great questions! 1. Generally, we leave the name blank when creating a field- that way the field is auto-named consistently, this is true for linked record fields too. Also, for formula fields, we always preface with a “fx” that way on zapier you know that it’s a formula field and don’t try to map variables to it. 2. Great call out! We normally create a section of views called “by field type” - then have views for only linked record fields, linked + lookup fields, only formula fields, and key fields to that specific table. Using sections to group things, like ⚡️Automated Views - really helps to keep things organized. Also, make interfaces instead of views to actually do workflows. Giving everyone edit access to the data just gets messy
