Tech Forum

The old issue that events must be created before classes are created to have lessons postponed rather than deleted still exits.

This is especially troublesome for events such as ward conference where the event will only affect select classes. When the event is created before any classes are created the only options are "All" or "None". The event will not affect all classes and selecting "None" precludes the ability to automatically postpone events. This creates a big workload to manually postpone lessons when the event is early in the year.

Yeah we know and it's on the list. (Reference 325, 403). Thanks.

I was toying with the idea of creating all the events, including ward conference as applying to ALL, then creating only those classes that are affected by ward conference, then editing the ward conference event to only apply to the currently existing classes and no longer to ALL, then adding all the other classes that will include stake conference and general conference... haven't tested it yet, but thinking it's a partial work around. Only works if ward conference is the only event like this and there is no overlap to other similar events.