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; } } }

De-mystify Experience Builder URL parameters

JayJohnsonWashoeCounty

When I navigate to different features in Experience Builder I see a URL that (apparently) includes some identifier related to either the feature I've clicked on or maybe the location. Can anyone de-mystify the RED part of the Experience Builder URL below? Maybe Jianxia Song‌?

https://experience.arcgis.com/experience/2fe9e44b691a4e32a9f0b84df16531c0?data_id=dataSource_3-ElectionGeography_795a03f022d2420ca49bf52b79aa80b5_5103_3112_2857_6478_6139%3A414

Obviously, what I'd like to do is be able to build URL strings to be able to direct users from an external web page to a specific location/feature within Experience Builder.

However, even though this portion of the URL appears to change as you navigate to different features/locations, it doesn't APPEAR to do anything at all if you past the whole URL into a new browser tab.

Thanks,

Jay

Najděte více příspěvků označených jako

Accepted answers

JianxiaSong

Jay,

Unlike Web AppBuilder, Experience Builder uses the structured URL. As a result, the URL for an experience contains its state information directly, so a user can easily share, without relying on a dedicated state component such as URL parameters in WAB, in order for others to see the experience in the same state. The structured URL is made up of the URL path and the URL parameter. The URL path is constructed for an experience or a web site to be deeply indexed therefore easily searchable by Google and other third-party search engines. The experience id and page default to the URL path, for example, <root path>/<appId>/page/<pageId>. On the other hand, the view, data, and others follow the URL parameter (aka query parameter), commonly used by ArcGIS web apps. For example, ?views=<viewId1, viewId2> defines which views to show when an experience is loaded. An experience url may look something like this:

<root path>/<appId>/page/<pageId>/?views=<viewId1, viewId2>&data_.id=<1>

Currently, Experience Builder has these main URL query parameters:

?views=v1, v2,..: As Experience Builder supports multiple views in a page, this stores user currently selected views
?dlg=dialog1: this stores user currently opened dialog (window)
?data_id=dsId:id1+id2 : this stores user currently selected data records

Although the example you mentioned does not seem making any difference, the following example shares the exact state I am seeing with you other than the default:

//experience.arcgis.com/experience/5947e2d55c1846e1b4952851aa97efe8/page/page_5/?data_id=dataSource_1-Fun_5299%3A4&views=view_2

Does it make sense? I would recommend to use the Share widget to get the shorten url for sharing though, if applicable. Also. would it be helpful if we document the url pattern as mentioned?

Thanks,

Jianxia

All comments

ANRGIS

Totally agree. I've been banging my head trying to figure out how to select a layer in our ExB application using a coordinate, but can't seem to figure out exactly what I'm doing wrong. <Geometry JSON> is not entirely helpful, especially if the application is picky about how it's formatted. What would be fantastic is having a tool/utility for building a URL with parameters based on the widgets/data sources you have in your map. Hacking the "share tool" shouldn't be the method for doing it and it is not helpful for capabilities such as selecting data. The resulting URL is essentially the selection once it's been completed, not the query itself.

TimConfare2

I totally agree. I've tried everything given the "documentation" but nothing works. I would also like an example from the developers version as that appears to be different then the online version.

amitchinson

How do you dynamically use URL parameterisation to select data by ObjectID? I've looked at the documentation here

https://doc.arcgis.com/en/experience-builder/latest/build-apps/url-parameters.htm#ESRI_SECTION1_0A01682276CD4E7985CA7E222BD648C1

and it looks like this is the relevant example and which would get the feature with ObjectID 1:

https://experience.arcgis.com/experience/<AppId>/#data_s=id:widget_1-dataSource_1-1871234a785-layer-2:1

I have a Survey123 form which is within an Experience. I'm trying to use URL parameterisation to create a dynamic URL at the end of the form/on form submission, which will take the user to a map page in the Experience and use the ObjectID to select the data point they just created. So I want to pass the ObjectID value in as a parameter to the URL.

I have it working to select the point using a where clause with globalId below

https://experience.arcgis.com/experience/<experience ID>/page/<page name>#data_s=where%3A<data source and layer>%3Aglobalid%3D'@[globalId]'

But when I try replacing globalId with objectId it's not returning any objectID values (I don't think it's recognising objectId as a valid field, although it's definitely in my data feature service).

SStopyak_BruceHarris

The URL Parameters documentation gives examples of URLs for different queries but not enough information for folks to be able to figure out how to build them.

JoabelBarbieri

Thanks. It seems now in March 2024 it's available but I couldn't make it work. Documentation is very poor. We need more examples and a ArcBlog post about it. Thank you

JianxiaSong

@JoabelBarbieri , Currently it is on the track to be available in Q1 2024.

JoabelBarbieri

Waiting anxiously for url parameters for coordinates. I really hope it's Q1 24 and not postponed again!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

AlejandroMari1

@Jianxia , will there be an option not to show any url parameters and have just the base url display?

JianxiaSong

Support for the app url parameters interaction with the map is slated to Q1 2024, including defining the scale, scale level, center at, query features, etc.

JoabelBarbieri

Hi. I'm also struggling to replicate my WAB portals using EB. For instance. I have a script that sends out a link to the web map with coordinates to open WAB Map centered in a coordinate. In WAB it's easy, just passing the parameter &center=-93.75767223%2C30.89139665&level=14

How do I implement this same thing in EB? Please help

MarkEastwood

@Jianxia - Is there any way to zoom to the filtered records in Experience Builder using URL parameters?

JianxiaSong

@ForrestSherman2 The app above does not seem shared publicly. Could you do the followings:

1. Make sure where clause is correct. When a value is type of String, use single quote.

2. In the browser console, type _appState.appConfig.widgets['widget_34'].useDataSources[0].dataSourceId to get the data source ID. here, widget_34 is an instance of the filter widget.

ForrestSherman2

Jianxia,
This did not work for me.
https://experience.arcgis.com/experience/6bd33b2f908b4e978873f7f15db5f8b6?data_filter=dataSource_1-Parcels_for_San_Bernardino_County_8504%3APN=%27043424422%27
Forrest

JianxiaSong

The URL parameters documentation is now available, including the data source id and filter parameters which you can use to perform filtering when the app opens. The URL parameters are grouped into three categories: general, data related, and login related parameters. More URL parameters will be added through incremental releases.

https://doc.arcgis.com/en/experience-builder/latest/build-apps/url-parameters.htm

Thank you for your patience!

JianxiaSong

@AnnaHradecká and @Anonymous User, thank you for your feedback. We plan to document these url parameters and will inform of you.

AnnaHradecká

Hi,

I¨ve read conversation below, but still don't understand the the mysterious string of number as @JayJohnsonWashoeCounty refer. ;What type of ID is used after "%" and is it possible to change it to more useful one to navigate to feature only by change the id in URL?

Anonymous User

Hello, Jianxia! It has now been 17 months since this comment^ Is the road map near completion? My team would love to be able to share a link and have it zoom to the extent like the Web Maps.

Brenda

ZachBodenner

Is there an update on the road map for when zoom and center can be added to URLs?

I have a Experience that is an interview where the respondent is talking about specific locations. In another page, I have a full-screen web map, and I want to have links in the interview that open that map page centered on the location the interviewee is talking about. Currently it does not seem like this is supported? (ExB 1.7)

cw_mund

We are currently deploying ArcGIS Enterprise. With ExB being the future, we have moved forward with our development in that environment.

Throughout Western Australia Local Governments, we have a common parcel ID commonly (and somewhat creatively) known as the Polygon Number. This is used as the primary key between various systems. We rely heavily upon this ID to quickly navigate between multiple systems.

We are replacing an existing system that has the capability of switching between multiple different maps and retaining the current extent (and even selected feature). I know there have been a few app switcher application in WAB to enable users to switch between apps and retain the current extent.

At the moment I'm building this within ExB, putting over 10 maps into a single app. This is proving to be system intensive as well as the maintenance will a lot more complicated. We have a lot more maps to come...

If there is anyway to have Querystrings made as a priority would be awesome!

Anonymous User

Any update on this @Jianxia ?

AlejandroMari1

Hello @Jianxia I found a good use case for disabling the URL parameters: sometimes ExB generates URLs that are longer than 2048 characters, which some web servers don't support (our IIS are configured not to allow URLs longer than that). I've summited this as a separate question to see if someone has a workaround for this, as this is causing us some problems, but I thought I'd mention it on this thread.

EmilyMcLeanACTGOV

Hi @PeterKT

This blog post might be able to help with your question.

Thanks,

Emily

EmilyMcLeanACTGOV

Thanks for the response @Jianxia !

For anyone interested, I have also logged this as an idea: Experience Builder Widgets to Support URL Parameters

JianxiaSong

Hi Emily, this would require widgets to support URL parameters, which is not available yet. It would be great if you can summit an enhancement to Esri Support.

EmilyMcLeanACTGOV

Hi @Jianxia ,

Just wondering if there is a url parameter to display a specific sheet within a table?

Thanks,

Emily

PeterKT

Hi,

How would you zoom to a feature on the map using the url parameters. I can get the url params to open the window and it highlights it in my list in the page. But my zoom to feature is on list selection which appears to not to be selected using the url params.

Any ideas?

Thanks

JanSarata

Hi @Jianxia ,

firstly, thank you for you respond.

Secondly, the reason to switch url states off is to ease the process of testing new Experience Builder app/widget while developing. If I need to refresh the app/builder to see the changes, the state is preserved. But in some testing scenarios it would be fine to have it always at its initial state.

So basically the reason is for testing/developing purposes.

Thank you,

Jan

JianxiaSong

Hi Jan,

Would you mind letting us know the reason that you'd like to turn off the state parameters in URL?

Yes, adding more state parameters like zoom and extent, similar to WAB url parameters, is on the road map. Will update you once we have a timeline.

Thanks,

Jianxia

JanSarata

Hello @Jianxia ,

I would like to ask you for the additional questions to this topic.

Is it possible to turn off this functionality? Turn off this automatic state parameters in URL?
Do you plan to add another state parameters such ZOOM or EXTENT?

Thank you in advance for you answer.

Jan

JayJohnsonWashoeCounty

Thanks Jianxia. Yes, documenting the URL pattern was exactly what I was looking for.

I'll try to work with what you have above to see if I can get where I need to be.

From within my Experience, I click on a specific feature and the webmap pans to that feature. The URL in the browser becomes this:

https://experience.arcgis.com/experience/2fe9e44b691a4e32a9f0b84df16531c0?data_id=dataSource_3-ElectionGeography_795a03f022d2420ca49bf52b79aa80b5_5103_3112_2857_6478_6139%3A397

The first part is my ExpBuilder app URL and the hosted layer that contains the feature I've clicked on:

https://experience.arcgis.com/experience/2fe9e44b691a4e32a9f0b84df16531c0?data_id=dataSource_3-ElectionGeography_795a03f022d2420ca49bf52b79aa80b5

But AFTER that, there is a mysterious string of numbers that I can't interpret: _5103_3112_2857_6478_6139%3A397

It does not appear that those numbers are a straight-forward reference to the selected feature.

Jay

JianxiaSong

Jay,

<root path>/<appId>/page/<pageId>/?views=<viewId1, viewId2>&data_.id=<1>

Currently, Experience Builder has these main URL query parameters:

?views=v1, v2,..: As Experience Builder supports multiple views in a page, this stores user currently selected views
?dlg=dialog1: this stores user currently opened dialog (window)
?data_id=dsId:id1+id2 : this stores user currently selected data records

Although the example you mentioned does not seem making any difference, the following example shares the exact state I am seeing with you other than the default:

//experience.arcgis.com/experience/5947e2d55c1846e1b4952851aa97efe8/page/page_5/?data_id=dataSource_1-Fun_5299%3A4&views=view_2

Does it make sense? I would recommend to use the Share widget to get the shorten url for sharing though, if applicable. Also. would it be helpful if we document the url pattern as mentioned?

Thanks,

Jianxia

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

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