Bug with "Enable search" in ArcGIS Enterprise

[mmoosbac94]

I'm not sure if this is the right place to report this issue, but we've encountered a bug in ArcGIS Enterprise related to the "Enable search" setting in maps.

When you activate "Enable search" after creating a map and configuring the layers, searching within the map's layer features works as expected. However, if you later make changes to the map and save it, the "Enable search" setting remains enabled, but search functionality stops working in the iOS app.

As a workaround, disabling and re-enabling the "Enable search" setting restores functionality.

Are you aware of this issue?

[mhdostal]

@mmoosbac94 Can you describe in a bit more detail the workflow you are having issues with? What search functionality (or APIs) are you using in the iOS app?

[mmoosbac94]

@mhdostal We are using the ArcGIS Swift SDK and ArcGIS Enterprise. In our app, we use the queryFeatures method for layer search, which generally works as expected.

The issue arises in the following workflow:

1. You create a map with layers.
2. You enable the "Enable search" option in the map settings.
3. Everything works fine, and we receive the expected results in the iOS app.

However, if you make any changes to the map and save it (in ArcGIS Enterprise map viewer), searching for layers stops working in the iOS app. The issue persists until you disable and re-enable the "Enable search" option. It seems that the "searchable" information is lost whenever the map is modified and saved.

[mmoosbac94]

Are there any updates on this?

[mhdostal]

Are there any updates on this?

Sorry for the delay, we've been busy with the 200.7 Release, but now that that's out the door, someone will be looking at this.

Thank you for your patience!

Mark

[mhdostal]

@mmoosbac94 I've dug into this a little bit, looking at the web map JSON w/regards to the "Enable search" functionality. I've used the ArcGIS Online Assistant site to examine the JSON and Data for a web map on an Enterprise portal. The JSON around the "Enable search" option does not change if I make an unrelated change to the map.

Some questions to help reproduce/resolve this:

• What version of Enterprise are you using?
• Are you using the Enterprise "Map Viewer" or "Map Viewer Classic" when making changes to the web map
• Using the ArcGIS Online Assistant above, do you see differences in the web map JSON after making the changes you mention? Use the "View an Item's JSON" option and select the map you want to examine:

I see the following in the "Data" section (bottom half of the view):

    "applicationProperties": {
        "viewing": {
            "search": {
                "disablePlaceFinder": false,
                "enabled": true,
                "hintText": "Place or Address",
                "layers": [
                    {

That section doesn't change if I make an unrelated edit to the web map.

• What kind of layer are you searching? Is it a feature service or a feature layer saved to the portal (not sure that matters, I'm just trying to figure out why I don't get the same results as you).
• What version of the Swift SDK are you currently using?
• Does this happen on a device (iPhone/iPad) or in the Simulator (or both)?

Thanks, hopefully we can figure this out.

[mmoosbac94]

@mhdostal Thanks for your effort on this. I took a closer look into the issue and was able to identify the cause. The problem only occurs when using the new map viewer — the old one behaves correctly and thus searching in layers works for us.

When using the new map viewer, we receive slightly different versions of the map JSON depending on whether the map is edited and saved after enabling search in the settings. The JSON from the old map viewer, or from the new one if the map is not edited after enabling search (which I assume is the correct behavior), includes an empty "tables" array parameter. However, if the map is edited with the new map viewer, the "tables" parameter disappears.

This was the reason our JSON decoding failed in the iOS app. We were able to fix the issue on our end by handling the "tables" parameter as optional, but I believe this behavior in the new map viewer is unintended?