Pulldata fields retaining irrelevant info when editing/using favorites in a new survey

[spf999]

Hi all, 

I am looking for a solution to this issue. I have a survey that combines three prior surveys. In mainly the monitoring portion of the survey, I have implemented the pulldata feature for some of my data fields. I ideally want to pair this with QR codes that should eliminate the need for the favorites feature; however some field staff may not choose to use the QR codes. I need to retain the ability to use the pulldata feature or have manual entry of data. With this being said, when I try to edit a submitted record or copy favorites to a new survey, some of the pulldata fields that have dependent questions are not cleared when they are submitted. This is resulting in messy data, by having the no longer relevant dependent fields, still being present (although not visible to the user in the form). For example, if I submit that a sample is a filter in the first initial survey, the pore size, smith-root backpack serial number, and the smith-root sample ID fields should all be submitted. This currently works well. However, if I were to copy this survey's info to a new survey and change the sample to centrifuge (no dependent questions), the pore size, smith-root backpack serial number, and the smith root sample ID fields are all retained and submitted (without the user seeing these responses), when it is not relevant anymore. I've attached my current XLSX form and thank you in advance. 

[spf999]

Hi @Neal_t_k, 

Yes, these two fields have been blank since we began discussing this issue and I believe this is how I originally set them up (without success 😞). As of right now, I have the field reviewed their submissions in the sent box after sending and I do an additional QAQC step after all the records for that project are submitted. I have not explored the dashboard option yet, but perhaps this is something that I can and should implement in the future. Thanks again for all your help! It's much appreciated! 

[Neal_t_k]

@spf999 One more try.  Your choice filter may be causing the issue....

for both sampinfo_type" and sampinfo_prestype"  try changing the choice filter to just  contains(projecttype, ${projecttype})

I think the "code=..." part of your choice filter is unnecessary  as it is referencing the question itself, so sort of cyclic dependency going on, but that along with, in your pulldata2026.csv, the samptype is all lowercase and the choices on the choice tab have the names capitalized which is causing a mismatch. So try one or both of those and see if that helps.   

If you just change the choice filter first, you will notice the pulldata works but it is in red as it doesn't match the choice filter, which when you have the code=... part actually stops the pulldata from populating.

 

Also you may still have to experiment with the calculation mode.  Currently set to "always" which may cause it to recalculate it on a re-open.