Select to view content in your preferred language

Expereince Builder URL parameters data select not working

254
4
Jump to solution
3 weeks ago
Labels (1)
HeathAnderson
Frequent Contributor

Hi all,

I'm trying to create a URL parameter in Experience Builder (ExB) while working in ArcGIS Enterprise 11.3. I've followed the documentation and successfully implemented a "data_s=where:" statement in ArcGIS Online, but I'm having trouble replicating that success in Enterprise.

📄 Reference documentation:
Experience Builder URL Parameters (ArcGIS 11.3)

🔧 Here's the example I'm working from:

 

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

#TESTING URL
https://<organization portal url>/apps/experiencebuilder/experience/?id=<experienceID>#data_s=where%3A<dataSource value>%3A<attributeField>%3D<attributeValue>

So far, I've been successful using OBJECTID as the attribute field, but I can’t seem to get it to work with other attribute fields. I’ve double-checked field names, data types, and syntax, but no luck so far.

Has anyone encountered this in Enterprise 11.3 or have any tips on what might be causing the issue?

Any help would be greatly appreciated!

Cheers,
Heath

Tags (3)
1 Solution

Accepted Solutions
Allen_Zhang
Regular Contributor

Sometimes the displayed field name is not the real field name...

Allen_Zhang_0-1745462682756.png

 

You can find the real field name here in arcgis rest service.

Allen_Zhang_1-1745462801529.png

 

And if the field is a text/string, you need to wrap the field value with single quotes:

Allen_Zhang_2-1745462876555.png

 

View solution in original post

4 Replies
Allen_Zhang
Regular Contributor

Sometimes the displayed field name is not the real field name...

Allen_Zhang_0-1745462682756.png

 

You can find the real field name here in arcgis rest service.

Allen_Zhang_1-1745462801529.png

 

And if the field is a text/string, you need to wrap the field value with single quotes:

Allen_Zhang_2-1745462876555.png

 

HeathAnderson
Frequent Contributor

Hi Allen,

It was the quotes.

Thank you

Heath

0 Kudos
PSRFA_GIS
Emerging Contributor

Thank you!  Where in the documentation does is mention strings must be in single quotes?  How did you know that?  I assumed double quotes and it wasn't working at all for me.  But that was just a wild guess due to no documentation on this subject.

0 Kudos
Allen_Zhang
Regular Contributor

Just a programmer's wild instinct!

0 Kudos