Continuing the conversation from here (auto-closed because I went on vacation 
): Auto-fill activity logs individual entries - #2 by Stephen_Hornak
@Stephen_Hornak Sounds like I didn’t describe the problem clearly enough. Here’s attempt #2.
Yes, you can enter a single set of days, nights, and frost points for the entire group using the “groups” tab and varying values for each youth & adult using the “individuals” tab.
The problem: while values for days, nights, frost points on the “groups” tab are pre-populated with the expected number of days & nights (based on event start date/time & end date/time), the values on the “indviduals” tab are all zeroes. The “individuals” tab is not pre-populated (or updated from what is user-modified on the “groups” tab cells).
It’s a small issue when you only have 10 attendees at an event. But it’s a much larger issue when you have 40, 50, or even 80. (Our troop is 52 Scouts plus leaders, our pack peaked at 90+ Scouts plus leaders last year.) For our recent troop summer camp, I had to manually enter days/nights values for all ~45 attendees because one single Scout and two leaders had different arrival/departure dates. Right now, the simplest work-around is to create separate camping activities for each group with the same number of nights/days (in the summer camp example, that would be pretty tedious and make our activity log cumbersome: four separate events–one for the “normal” group and one for each “odd” participant, as they all had slightly diffrent counts).
The simplest recommended solution: pre-populate the days/nights on the “individuals” tab using the same logic that the “groups” tab is pre-populated. Then activity editors only have to edit the exceptions.
Better solution (but possibly not feasible): pre-populate the “individuals” tab based on what is modified in the “groups” tab and save values based on what’s in the “individuals” tab (if modified). This addresses the situation of other activity logs (esp. hiking, where “groups” and “individual” values are pre-populated with zeroes; and to a lesser extent service hours, where pre-populated values based on event duration may need to be reduced for actual time service is performed).
