Hey ​@Judy12  the problem here is that he Date field is something you need to input either manually or with an automation.

The quickest solution is changing the type of the primary field to a Formula that references the linked record that is the date of march.

Hmm, is the value in the “Date” field always the same as the value in the “Day of March” field?  If so, I’m wondering whether you could just replace the primary field with a formula field that displays the linked field value like so:

Base design wise I think that looks fine!  

Hi ​@Judy12,

In the table where the date isn’t appearing in the primary field, you could turn that primary field into a calculation field that equals the linked record field that is showing you the date. Your formula could be something like this:

{Day of March_} & ""

Alternatively, you could keep your primary field as a date field, and just use an automation to automatically update the primary field with the date whenever the linked record field is updated.

Hope this helps!

If you have a budget and you’d like to hire the best Airtable consultant to help you with this or anything else that is Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld

Oops, I didn’t see that 2 people had already responded above with the exact same advice as me! :)

- ScottWorld, Expert Airtable Consultant

So...after I posted this I thought I would try just swapping out the date with the Event Name, then just deleted that date field. So now the Event Name is the primary field, and it’s working.  But now I know about calculations, and I see there are consultants, so that’s great for the future.  Thank you!

Yep, I think you got it figured out, but I’ve found it generally useful to create separate tables for Event and Date as often enough an event is either across multiple days or is recurring in some manner. In that setup your event name is primary, and the other table has date as it’s primary. Just something to consider in the future