Data Collected using Mobile Patrol Package Importing as Survey Data

SMART Community Forum
1

Hi There

A bit of a strange one. We converted some tree attributes in our Data Model into multi-select lists as we needed a multi-select functionality and trees cannot be multi-select (a feature that would be amazing if possible!). Basically, we disabled the old tree attribute, and created multiple multi-select attributes that captured the same data as the tree nodes once did. In the Configurable Model (CM), we selected the option to “collect multiple observations” for our new multi-select lists. We otherwise had the exact same CM format as our previous, tree-containing CM, and exported this to SMART Mobile using a patrol package.

We collected trial data, and when we opted to import the data from the phone, SMART automatically asked us to create a new survey and mission, as if we were importing Survey Data. Does anyone know why this is happening? Is there any work around, as it doesn’t make sense for this data to be in a survey format?

Thank you very much for the help.

All the best
Mich

2

Hi Michelle,
My guess would be either :

  1. There was some other, actual survey data on the phone that happened to get imported when you weren’t expecting it; or
  2. That it was a mistake when creating the new “package” and it was accidentally created as a “Survey Package” instead of a “Patrol Package”. Try recreating a new Patrol package and testing again in this case.

SMART Mobile treats the two types (patrols and surveys) quite differently, so I don’t think it is likely for patrol data to trigger the new-mission action upon data as you saw if everything was setup to collect patrol data.

3

Hi Jeff

We have not encountered the issue again so it must have been one of your above explanations. Thank you very much for getting back to me!

All the best
Mich