nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

URL parameters no longer work with new map viewer

ahargreaves_FW

Hello,

I'm trying to use a URL parameter to search out a uniqueID and highlight the feature in a webmap with a URL parameter that use dot work for a webmap build in "classic".

The uniqueID is created as a string using #Survey123.

The webmap has the uniqueID field included in its searchable layers.

However, the url parameter shown below now no longer works since migrating the map to the new map viewer:

https://xyz.maps.arcgis.com/home/webmap/viewer.html?webmap=cxxxxxxxxx9?find=0xxxxxx5

Trouver plus de publications taguées avec

Data and services

Mapping

Accepted answers

RussRoberts

It is available in the Map Viewer. Here is a sample URL

https://jsapi.maps.arcgis.com/apps/mapviewer/index.html?webmap=5091d48b9a5b40449a225c335102c026&find=511662

All comments

JohnCoddHere

That is frustrating!

SzuNyiapTang

Hi @ahargreaves_FW

According to the documentation, it should work for both Map Viewer.

for the new Map viewer https://xyz.maps.arcgis.com/apps/mapviewer/index.html?webmap=xyz&find=xyz

View this example in Map Viewer

Cheers,

Tang

ahargreaves_FW

@SzuNyiapTang but it doesn't work - hence why I posted.

The example you link to is searching for an address searched against the esri geocoding service. My example looks to search an attribute in a layer included n the webmaps search settings. If I've done something wrong, or misread the documentation, please let me know.

RussRoberts

It is available in the Map Viewer. Here is a sample URL

https://jsapi.maps.arcgis.com/apps/mapviewer/index.html?webmap=5091d48b9a5b40449a225c335102c026&find=511662

ahargreaves_FW

hmmm...OK, thanks @RussRoberts for sending me down the right path. So this was interesting. Here's my theory:

Before posting this thread I had manually edited my webmaps JSON to include ObjectID and GlobalID as search parameters in an attempt to use those:

"search": {
"disablePlaceFinder": false,
"enabled": true,
"hintText": "Place or Address",
"layers": [
{"field": {
"exactMatch": true,
"name": "objectid",
"type": "esriFieldTypeOID"
},
"id": "xyz"
},
{
"field": {
"exactMatch": true,
"name": "globalid",
"type": "esriFieldTypeGlobalID"
},
"id": "xyz"
}

2. Once they failed to work I established a UniqueID calc’d through Survey123.

3. I updated the webmap to use that in it’s search criteria instead. But it never did. Hence this post.

4. Upon checking the JSON for the webmap it appears that, perhaps by previously manually editing it, step #3 above never took. And the webmap never actually had my UniqueID set as a search criteria in it’s JSON, despite showing me it did through AGOL GUI.

5. I manually removed ObjectID and GlobalID from the JSON, and manually added in UniqueID….voila! it works.

JeremyNickel

At this point, it feels less like progress and more like forced compliance through broken backward compatibility. Esri used to be a tool that made my job easier—now it’s a constant cycle of chasing bugs and rebuilding work that already functioned. That’s not innovation; that’s inefficiency.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.