Feature Requests

Allow custom fields to be selected when controlling column visibility
The ability to map custom fields to forms is an awesome feature. It has allowed us to standardize the way we gather our data. We can now provide a dropdown to the parents that asks, "Does your child have an EpiPen?" or "Is your child lactose intolerant?" etc. and get a yes or no, boolean answer. The reason this is so great is because we no longer have to deal with allergy submissions that look like this ("asthma, pollen, peanuts, tree nuts, EpiPen, lactose intolerant - EpiPen for tree nuts and peanuts”). It also allows us to do other things we couldn’t do before like differentiate between food allergies and environmental allergies, food restrictions and food preferences, etc. while flagging priority information like EpiPens, Lactose Allergies, specific diets, certain photo permissions, and more. However, because there is no way to display or prioritize these custom fields, it reduces how often we can actually utilize them because of the potential that the default fields could mislead. For example, the “Allergies” default field currently contains ALL of the Child’s allergies (food AND otherwise). This has been a pain point for us in the past because the field usually ends up also including food restrictions and food preferences, often with confusing syntax and no consistency. And with multiple schools, the problem is compounded. However, your custom field feature basically solves this problem outright and gives us full control over how we collect and organize the data, while even allowing us to apply the fields to ALL schools. It’s exactly what we needed. There’s just one small catch - Since we don’t have the option to display our custom fields like “Food Allergies” in lieu of the default fields, we run the risk of a teacher referencing the default “Allergies” field when checking for food allergies while the actual “Food Allergies” exist in a field that is effectively hidden. This is also the problem with our “EpiPen” boolean field which exists for a couple of reasons - 1. To enable conditional fields in forms and 2. To prevent “EpiPen” from getting lost in the list of medications. Again, we can’t really use this field due to the risk that a teacher will reference the “Medications” default field when looking for EpiPens. To summarize, it would be great if the custom fields we create were included when using the “Adjust Columns” feature on the Students tab (My School > Students) AND within each specific classroom (My School > Classrooms > [classroom_name]). Without the ability to do this, the custom fields can’t be utilized to their fullest without running the risk that important information is missed due to conflicting default fields.
0
Load More