<! ODK Entity Challenges in Outage Reporting – Looking for Solutions
Greetings everyone, my name is Onyali Forbes, I work with the electric utility company in Guyana. Ive been working on improving our outage reporting process using ODK. I was able to build a form and upload it successfully to Central, and I even created the entities dataset with all the properties linked to the form. However, when I fill out the form, the details don’t actually get saved into the entities dataset, even though everything looks connected.
My main goal is to have one form that can either create a new outage or update an existing one. I’ve tried designing it so the user first selects whether they want to create or update, but making sure only the right fields and entity actions run has been tricky. If both workflows trigger, I get errors with missing UUIDs or invalid entity references.
So I’m reaching out for advice. Should I keep the create and update process in one form with strict relevant conditions, or would it be more reliable to separate them into two forms? And when updating, is it better to show old answers as read-only notes, or have them pre-filled in editable fields? I’d really appreciate any insights that could help make this outage reporting process smoother and more reliable.