Notice that as time goes by, you keep needing to add new columns. In general, this is very common for a spreadsheet, but bad practice for a database for like Airtable.
Instead I recommend a two table system. On table for your preschool names, and another linked table for the months. The months table would have three columns: the link to the preschool, the month (probably represented by a date field with the first of the month), and the number of children.
This way as time passes, your table gets taller instead of wider. And you are back to the process of finding the latest row in a set of linked records.
Notice that as time goes by, you keep needing to add new columns. In general, this is very common for a spreadsheet, but bad practice for a database for like Airtable.
Instead I recommend a two table system. On table for your preschool names, and another linked table for the months. The months table would have three columns: the link to the preschool, the month (probably represented by a date field with the first of the month), and the number of children.
This way as time passes, your table gets taller instead of wider. And you are back to the process of finding the latest row in a set of linked records.
Thanks so much. So like this?
And then just add a new set of rows for each month?
Thanks so much. So like this?
And then just add a new set of rows for each month?
Almost. Instead of having your preschool names in the primary field, create a new linked record field to a new table with one row for each preschool. The primary field can then be a formula field that combines the preschool name with the month.
Then in the table of preschools, you can have rollup fields that tell you things like, average enrollment per month, enrollment for the current month, etc. This support page can help you get started with rollup fields. You can also look at the other posts on getting the lastest linked record.
Almost. Instead of having your preschool names in the primary field, create a new linked record field to a new table with one row for each preschool. The primary field can then be a formula field that combines the preschool name with the month.
Then in the table of preschools, you can have rollup fields that tell you things like, average enrollment per month, enrollment for the current month, etc. This support page can help you get started with rollup fields. You can also look at the other posts on getting the lastest linked record.
Is this better?
Then I would do the roll up under the other table (ECDs)?
Almost. Instead of having your preschool names in the primary field, create a new linked record field to a new table with one row for each preschool. The primary field can then be a formula field that combines the preschool name with the month.
Then in the table of preschools, you can have rollup fields that tell you things like, average enrollment per month, enrollment for the current month, etc. This support page can help you get started with rollup fields. You can also look at the other posts on getting the lastest linked record.
I think I got it! Does this look right?
I think I got it! Does this look right?
Looks good!
Depending on your data entry process, you might need to adjust your rollup configuration.
I also recommend that you combine the two tables of numbers into a single table with both/all years. That way you will not need to modify your base structure as the years go by. To see the individual years, use filtered views.
