Mobile Commnons: Location based mData is not responding correctly with locations
Environment
Mobile Commons
Resolution Summary
I first tested the mdata and it was working fine. I continued to dig and check why this was not working at the time the client reported it. Details below.
I've done some digging here and I see that this is related to the mData taking some time to geocode the new entries uploaded. Correct me if I'm missing anything here, but I see multiple attempts to upload the list of 9k+ entries/locations to multiple versions of the mData. In general, the system would need some time to geocode all the entries. With multiple upload attempts, I believe this added more and more records in the queue and caused a delay in geocoding all the records.
To be able to use the mData and get results, the entries should be fully geocoded and show up like this screenshot below. At the time you tested, the entries were not geocoded yet, so there were no results to return, etc.
Details
Reported Issue/Question
The mdata is not sharing the locations/outputs when someone texts their location. I’ve been trying for hours. Are you able to assist?
The mData in question (link below) is a location-based mData where the user can text in a keyword and search term (address/location) and get a response with the closest safe place.
MDATA: English_5.12.23D | Mobile Commons (mcommons.com)
Internal Information
Resolution Category
Question::Product Consult / Strategy
Keywords
mData location_based raexternalrequest