/
GIS configuration did not carry over after upgrade
GIS configuration did not carry over after upgrade
Description of Issue
Maps are missing in the Field Work and Asset Registry programs after upgrading
Upgraded to a new version and the GIS configuration did not copy over
Context
Enterprise Asset Management
EAM
Cause
GIS configuration does not copy over during a refresh or upgrade
Resolution
Go to Munis > System Administration > General Administration > GIS Configuration and click Import From File
Click Yes to import GIS configuration information
Select the GIS configuration file and the GIS configurations will import in
Additional Information
Support recommends exporting and saving a copy of your GIS configuration file any time changes are made to your configuration
, multiple selections available,
Related content
Error when updating Content Management URLs in Munis
Error when updating Content Management URLs in Munis
More like this
Add Custom TCM Mapping to Project Master following upgrade
Add Custom TCM Mapping to Project Master following upgrade
More like this
Default basemaps are intermittently not loading in Asset Registry or Field Work
Default basemaps are intermittently not loading in Asset Registry or Field Work
More like this
Map layers missing within Field Work and Asset Registry
Map layers missing within Field Work and Asset Registry
More like this
EAM asset fields are incorrectly updated after processing an asset import
EAM asset fields are incorrectly updated after processing an asset import
More like this
Feature Type not available in Asset Registry Data Sync
Feature Type not available in Asset Registry Data Sync
More like this