Thank you so much!
You’re right, Flow will be recorded numerous times a month in a Data Type: ‘log’. Also included in this data type will be the fields: symptoms, mood, energy levels etc.
1 Like
Great, then this will work perfectly for you! It sounds like you’ve already got the right idea for the fields on the log - just make sure you’re storing the responses (e.g mood, energy) as the relevant option sets rather than as texts.
1 Like
Ohh! The fields are currently set to text/numbers/lists of texts (depending on the input type).
Is it essential to change it to store the responses as option sets rather than texts/numbers/lists of texts etc?
Can option set fields hold multiple options? I’ve configured it so that multiple symptoms and moods can be inputted during the ‘daily check-in’.
I’ve tested it and it does store the data in the database - but I’m a bit worried it may be breaking something I’m not aware of 
There’s a case to be made that something like energy level/intensity/productivity might be stored as a number, because these are all values which are measured on a sliding scale. I would probably use option sets as it’d be easier overall (you can reference Log’s Option and save Log’s option rather than having to convert between numbers and options).
Let’s look at ‘Energy levels’. You’d want an option set with options for Low, Medium, High for the user to select. Each option should have a ‘number’ attribute set to 1, 2, and 3 respectively. You’d display the option set in the repeating group to allow the user to select one, and when they save it, save the selected option’s number to the Log. If you wanted to store it as an option, you’d save the option itself to the log (as opposed to option’s number).
Physical symptoms should definitely be an option set (fatigue, cramps, etc) and you store a List of Symptoms on the log. Same goes for Mood.
1 Like
Ahhh okay!
Looking at your ‘Energy levels’ example, am I right in thinking that being able to store the selected energy level as a number (using an option attribute) is the only way to be able to report on it?
Currently, the energy level input in my app is a numerical sliding scale of 0-10. Same with productivity, motivation, confidence, creativity, focus.
Yeah, if anything has a sliding scale, you’ll be fine with using that data point as a number and it’ll be more straightforward to integrate in the editor. Can always change it later on if it’s needed. Option set would be preferable if you were display options (e.g Low, Medium, High) rather than a sliding scale.
1 Like
Awesome! thank you 