Resolving cloning issues in Indoor Mapping instances

  • Release version: Yokohama
  • Updated July 7, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Resolving cloning issues in Indoor Mapping instances

    When cloning an Indoor Mapping source instance to a target instance, administrators might encounter missing attachments and data inconsistencies. These issues primarily stem from the default cloning process excluding critical tables and attachments necessary for Indoor Mapping functionality. This can affect not only the Indoor Mapping data but also workplace experiences across related ServiceNow applications such as Map Studio, Workplace Central, Reservation Management, and others.

    Show full answer Show less

    Cause

    The cloning process excludes the Attachment [sysattachment] table and does not preserve data from key Indoor Mapping tables:

    • Font [snmapcorefont]
    • Layer [snmapcorelayer]
    • Outdoor style [snmapcoreoutdoorstyle]
    • Tile [snmapcoretile]

    This exclusion leads to missing data and broken references, such as missing JSON attachments in outdoor styles.

    Resolution Procedure

    • Export Data: From the source instance, export the records from the four critical tables as XML files.
    • Import Data: In the target instance, switch to the Indoor Mapping application scope and import the XML files.
    • Fix Missing Attachments: Because JSON files tied to outdoor styles may still lack attachments after import, complete additional preservation steps.
    • Preserve Data in Clone Admin Console: To prevent future issues, configure the Clone Admin Console to preserve data for the four tables by:
      • Navigating to Clone Admin Console > Clone Definition > Preserve Data in the source instance.
      • Adding entries for each key table to preserve their data during clone.
      • Associating these preserve data settings with your clone profiles.

    Practical Impact for ServiceNow Customers

    Following this procedure ensures complete and accurate cloning of Indoor Mapping data, preserving attachments and configurations essential for consistent workplace experiences. Properly preserving these tables reduces manual remediation after cloning and supports smooth operation across Indoor Mapping-related applications in your environment.

    After cloning a Indoor Mapping source instance to a target instance, workplace administrators may observe missing attachments and data discrepancies in their target instance.

    Symptom

    Administrators can clone a source Indoor Mapping instance to a target Indoor Mapping instance. For more information, see cloning an instance.

    Before cloning your Indoor Mapping source instance to a target instance, preserve data for each of the listed tables in your source instance. This helps in preventing missing data and attachments in your target Indoor Mapping cloned instance tables.

    Cause

    Data discrepancies and missing attachment issues are observed after you have cloned your target instance. The System Clone [clone_instance] record or Clone Request [sn_instance_clone_request] record in the source instance excludes the Attachment [sys_attachment] table and doesn't preserve data in the Font [sn_map_core_font], Layer [sn_map_core_layer], Outdoor style [sn_map_core_outdoor_style], and Tile [sn_map_core_tile] tables.These issues also affect workplace experiences in Indoor Mapping Map Studio, Workplace Central, Workplace Reservation Management portal, Workplace Services Kiosk, Workplace Move Management, and Workplace Service Delivery for Mobile.

    Resolution

    Procedure

    1. Log in to your source instance.
    2. Export the list of records in each listed table as XML from the source instance:
      • sn_map_core_font
      • sn_map_core_outdoor_style
      • sn_map_core_layer
      • sn_map_core_tile

      For more information, see Export data from a list.

    3. Log in to the target instance.
    4. In the target instance, update your application scope to Indoor Mapping.
    5. Import the XML files to the target instance.
      Note:
      After importing the XML files, it's observed sometimes that there's no data in the JSON files. The JSON files stored in the Styles (style) column of the Outdoor styles [sn_map_core_outdoor_style] show missing attachments. To prevent missing attachments and data discrepancies, perform steps 6-7.

      For more information about how to import XML files, see Import data from XML.

    6. To avoid future clone issues, preserve data in the following tables:
      • sn_map_core_font
      • sn_map_core_outdoor_style
      • sn_map_core_layer
      • sn_map_core_tile
    7. To preserve data in sn_map_core_font, sn_map_core_outdoor_style, sn_map_core_layer, and sn_map_core_tile tables perform the following steps:
      1. Log in to your source Indoor Mapping instance.
      2. Navigate to All > Clone Admin Console > Clone Definition > Preserve data.
      3. Select New.
      4. On the form, fill in the fields:
        Table 1. Preserve Data form
        Field Description
        Table Enter the following table information as required:
        • [sn_map_core_font]
        • sn_map_core_layer
        • sn_map_core_outdoor_style
        • sn_map_core_tile
      5. Right-click the form header and select Save.
      6. Add your clone profiles.
        1. Navigate to Clone profiles related list.
        2. Select Edit.
        3. From the Collection slush bucket, add your clone profile(s) to the Clone Profile List slush bucket.
        4. Select Save.