...
Copy TPK to a PC
Rename file from *.tpk to *.zip then unzip the file
Open the file \servicedescriptions\mapserver\mapserver.json in a text editor
Search for all instances of “mapScale”, and change any non-zero mapScale values to 0
Save mapserver.json
Select all of the folders that were in the TPK
Rezip all of the folders that were produced when unzipping the original file. The re-zip must be done without compression. This is the trickiest step, as the default windows zip tool cannot do this. You will need a zip utility like 7-zip that has the option to simply archive with no compression.
Rename file back to *.tpk
Copy TPK back to the appropriate folder in your MobileMap directory on your mobile device
Can I use the same base map TPK in MobileMap and Esri’s Field Maps?
My organization uses Field Maps in addition MobileMap. Both apps use base maps in TPK format and I would like to be able to make a single TPK file and use it in both apps. Is this possible and if so, how do I do that?
The short answer is that you cannot use the same TPK base map file with both Field Maps and MobileMap. The main reason for this is Android security - Android creates silos to protect apps from accessing other apps data. MobileMap uses a specific file structure and access data in that file structure is possible because the user grants permission when selecting their data directory in MobileMap. Field Maps using a different directory structure which it has permission to read and write data. It is possible to create a TPK and save it into two locations, one for Field Maps and another for MobileMap. This approach may be the most efficient way to create base maps, as it may cut down on the processing time for building TPKs. It will, however, require twice the data volume of the TPK since it will be stored in two different locations.
If this poses a significant impact to your organization please contact our team and we can explore options for enhancing MobileMap to
Why can’t I see any base maps in MobileMap?
...
MobileMap uses separate upload and download actions, rather than Esri’s ‘sync’ functionality when updating data. MobileMap’s upload/download is better suited to poor internet connections and provides better control over data by separating into distance upload and download actions, but has one major difference from Esri’s ‘sync’. In MobileMap, data deleted in a feature service are NOT downloaded as changes. This means that data deleted in InventoryManager, ArcGIS Pro or other tools will still show up in MobileMap even after a download. When deletes must be ‘pulled’ down to MobileMap, it is necessary to re-initialize and re-download to synchronize MobileMap’s data with the data on the Feature Service. Given this limitation, some users choose to use InventoryManager as a read-only tool for data review but not editing, or to use InventoryManager for updates only (no deletes), and use MobileMap for edits or deletes, respectively. Similarly, some users allow editing/deleting in InventoryManager only for a subset of their users (e.g., staff but not contractors).
...
Default values in MobileMap or InventoryManager
...
and ArcGIS Online
If you published your feature service from ArcPro either overwriting and existing service or publishing to a new service from an ArcPro map that was used previously to publish a feature service, try publishing from a fresh ArcPro project and publish to a new feature service not overwriting the existing one. Not ideal, but seems to resolve the issue. Clearing the cache in ArcPro or starting from a fresh map resolves the issue occasionally, but not consistently.
...