Editing a household unmaps that household
Posted: Wed Aug 22, 2012 3:00 pm
An unfortunate side affect of editing either emergency response text field, "Emergency Response" or "Special Needs", for a household is that the household location status changes to unmapped/"unknown location" and the location marker is removed from the map.
It appears that the edit option "Status" is defaulting to "unknown location", the first item on the list for status, when the "Categories" option is edited. The location status should not change unless user input is made.
If a category item is edited then the location status must also be edited to select the status that existed prior to editing to prevent the programming error from changing the location status to "unknown location".
Edit: Well, now the behavior has changed after several hours of testing to compose this post. I returned to LDS Maps to test another issue related to verifying a location and noted the behavior I reported above had changed (household status is not changing after editing emergency response categories). I hope it is because of program changes to Maps and not an issue on my end. The issue reported above had been occurring for over a week while I was verifying and editing emergency response data. I am leaving this post here as a reference should the issue repeat later.
It appears that the edit option "Status" is defaulting to "unknown location", the first item on the list for status, when the "Categories" option is edited. The location status should not change unless user input is made.
If a category item is edited then the location status must also be edited to select the status that existed prior to editing to prevent the programming error from changing the location status to "unknown location".
Edit: Well, now the behavior has changed after several hours of testing to compose this post. I returned to LDS Maps to test another issue related to verifying a location and noted the behavior I reported above had changed (household status is not changing after editing emergency response categories). I hope it is because of program changes to Maps and not an issue on my end. The issue reported above had been occurring for over a week while I was verifying and editing emergency response data. I am leaving this post here as a reference should the issue repeat later.