This proposal provides user-friendly XLSForm access to the remembering previously entered values feature. Implementation in pyxform depends on a decision at Spec proposal: add first-load event to replace xforms-ready . I propose adding a yes/no column to represent whether a particular question's val…

The ${last-saved#} syntax is now available in pyxform 1 and ODK XLSForm Online v2.0.0 . It is documented at https://docs.opendatakit.org/form-logic/#values-from-the-last-saved-record .

Thanks, that makes more sense. This is actually pretty much exactly what I do in GoMobile, except we call these 'entity' forms the "Asset Form" associated with an inspection. This basically holds/displays/captures the (mostly) static data about the thing you are inspecting; eg building address, owne…

EDITED to use last-saved instead of last as the prefix. How have the latest ideas aged through various showers/sleeps/brain marination sessions? Here is what I think the latest proposal looks like: If the contents of the default column are not a literal value, the expression is passed through to…

Yes, this looks good to me. Since we're introducing some major new syntax here, I'd like to make double triple sure that (a) this is consistent with any other similar syntaxes that already exist, and (b) it's flexible enough to cover a reasonable number of similar future requirements. As far as I c…

Agreed, @adam.butler . Would the TSC perhaps be willing to put this on the next agenda to discuss for 5 minutes and make sure we have considered every angle and that there is consensus to proceed? This has felt like a very good discussion with most TSC members involved but you're right that since it …

Wow, great discussion! I want to bring up one potential issue that I think hasn't been mentioned before, that may impact the design (if we cannot solve it in the pyxform implementation). On the XForm side, there is a subtle difference between using <setvalue> with the odk-instance-first-load event …

Overall, this looks great to me. Two nits to pick. The use of two underscores to prevent naming collisions is fine (seems to work for Python), but using it implicitly sets a standard for how pyxform generates these IDs. Are we sure this is the best syntax? I wonder if last is verbose enough. I…

Thank you, @martijnr ! That's an interesting case I certainly had not considered. Agreed it should be supported and adding a repeat-creation event seems like the best way to do it. There are already various cases in pyxform where the output is different based on nesting in a repeat so I don't think i…

Can't contribute to the technical conversation but I work for MSF (Medecins Sans Frontieres) and we have implemented an ODK-based hand hygiene compliance observation tool across multiple health facilities in 15+ countries. This feature was on our priority list for future versions so observers didnt'…

Hi, Pete! Great to see you here. This is the right place to be—it'll all get worked out on this thread; I'm guessing there will be more discussion in the coming weeks.

@pedrito1414 if you have feedback on the XLSForm structure as shown in the sample spreadsheet in this post from a user perspective, that would be very helpful! Is it intuitive? Does it serve the needs you have in mind?

ODK Forum

XLSForm spec proposal: add syntax to make it easy to use a value from the last saved instance

Development