I do something similar in my Wardrobe Manager base in Airtable Universe. Instead of [Contacts], I have [Garments]; instead of [Meetings], I have [Outfits]; instead of {Meeting date}, I have {Last Worn}. As part of the appearance-tracking portion of the base, whenever a {Last Worn} date is set for an [Outfit], that date is applied to all [Garment]s that make up the [Outfit]. (If the garment already has a {Last Worn} date later than that of the outfit, it doesn’t change.)
I think the applicability to your project should be obvious. :winking_face:
How does it work?
That’s a damn good question. Since it looks for the most recent of a group of dates, I would think I’m rolling up all the dates using a MAX() aggregation function and then setting a value for any record where {Last Worn] is equal to {Max}. I’d also guess I must be using a linked-record relationship between the outfit and garments to allow the outfit’s condition and worn dates to trickle down to its component garments. But I’m just guessing…
I’d suggest going to the base in Universe. Start by opening the [Documentation] table and viewing the attachment stored in the first record. This is the users guide; look for the brief sections on [Outfit]s and Appearance management. After that, go to the [Worn] table and examine the fields. (Each field has a description that explains its purpose within the base; the descriptions for formula fields contain the full formulas, as well, so you won’t need to duplicate the base simply to check configurations.)
You should be able to fit the code to your needs with relatively little 3ffort’’’
