1. What is the issue? Please be detailed.
I've uncovered a nasty little issue in my form that prevents it from loading in certain cases (I used last-saved for a field in a repeat, this causes a 'duplicate / try using indexed-repeat' error if the previously saved item populated this field with >1 repeat elements...), and I think I have users with existing drafts that will be affected and can't trash & redo these submissions with an updated definition.
I was hoping there was simple process I could get them to follow to clear the last-saved values if they do hit this error.
3. What have you tried to fix the issue?
I tried resetting 'Form load cache (.cache folder)' in project management settings, but this didn't work.
From the issue - it seems deleting last-saved.xml might do it - I located the file in the most recent definition folder and renamed it, this did clear the values in the next submission, but this is not an easy process for the users.
If the blank form opens for those users and the values you're using in follow up submissions are either blank or non-relevant at form load, your users should be able to open the blank form, use the floppy icon to save a blank draft, exit, open the draft that was failing and then blank values would be used where where last-saved is accessed.
If that doesn't work, you could change your form definition to clear out the default for the field that's later being used in a last-saved expression, have the users follow the process above, and then change the form definition back.
Basically you want to exploit the fact that last saved really is the last SAVED value and get your data collectors to save a blank value in the possibly faulty field.
We really do want to add functionality to force open a draft with a new form definition!
Ahh of course! I didn't even think of that. Simple fix if the issue occurs. (not yet, so I'm hoping I escaped this time)
This would be very helpful in many cases, (to get past foolish form authoring choices ), but there are definitely times you want the original definition to be used for an edit. If it was optional to select original or latest I think that would be ideal. This would apply to both unsent drafts and 'Edit x' drafts from already sent forms?
Agreed! I'd use it in particular when iterating on early drafts of a form definition. It'd be great to carry the same draft data over to new versions of the form definition even when the form definition could have changed quite a bit.
There's an Ideas thread about the general concept.
Yes, that's the idea. Probably available from the overflow menu (⋮) or something like that.
), but there are definitely times you want the original definition to be used for an edit. If it was optional to select original or latest I think that would be ideal. This would apply to both unsent drafts and 'Edit x' drafts from already sent forms?