|
POST
|
@Cory__Williams You can choose the Custom mode and drag & reorder the needed basemaps. Also, do you have some screenshots showing the differences between the widget vs. order set in the portal?
... View more
02-06-2024
01:03 AM
|
0
|
0
|
2131
|
|
POST
|
That would be something we can think about. It makes good sense with a 1-to-1 connection, however, given that we do not limit how many ML widgets are connected anymore, with a large amount of user requests, honoring which widget could be a problem. That said, feel free to add this to our Ideas channel. We will continue to watch the feedback and evaluate the possibility of an enhancement. Thanks for bringing it up! Tonghui
... View more
01-22-2024
05:54 PM
|
0
|
0
|
1606
|
|
POST
|
@AndreasEugster This is not a bug. In the previous release, we only supported 1-to-1 connect from a Map Layers widget to a Map widget; however, in the new release, we supported the connection to the same Map widget from multiple Map Layers widgets, meaning you can use ML1 to display layer ABC and ML2 to display layer DEF. These settings won't affect the map tool since it shows all layers by default. Tonghui
... View more
01-21-2024
07:11 PM
|
0
|
2
|
1618
|
|
POST
|
@DSteff We're not sure about your environment, but here is a similar post that you may find useful: https://community.esri.com/t5/arcgis-experience-builder-questions/getting-javascript-error-quot-s/m-p/1129405#M3415
... View more
01-19-2024
01:42 AM
|
0
|
0
|
988
|
|
POST
|
Hi there, the map extent issue is difficult to pinpoint just by looking at it. It would be better to reach out to Esri Support if you are still seeing the same issue. Thanks for brining this up.
... View more
01-17-2024
11:45 PM
|
0
|
0
|
1318
|
|
POST
|
Hi @ChrisRoberts2 Currently we do not support anchor link to screen/screen group, however, you can work around it by using a empty block on top of your desired screen group, and then link to block from Button/Image/...
... View more
01-17-2024
11:42 PM
|
2
|
1
|
2608
|
|
POST
|
Hi @Jennifer_Parmeley It looks to me like it has something to do with how you formated the pop-up information inside the Map Viewer. You can check if that's the same behavior in MV pop-ups. Generally, we do not control that part of logic in Experience Builder.
... View more
01-17-2024
11:24 PM
|
1
|
1
|
1328
|
|
POST
|
It sounds like the "Customize layers" inside the Map Layers widget could help with your case?
... View more
01-17-2024
11:14 PM
|
0
|
0
|
870
|
|
IDEA
|
FYI - this is not related specifically to the 'contains' operator - it is the current behavior because predefined values only support honoring all right now.
... View more
01-17-2024
11:03 PM
|
0
|
0
|
2213
|
|
POST
|
Hi @HaileyWright1 The issue you had here is not specifically related to the 'contains' operator. It is related to predefined values. ('Contains' operator only supports user input & predefined as sources) Given that predefined values could be manually typed in and do not have anything to do with the original data source (e.g. for domain fields, users can type in 1/2/3/... first and then update their subtype fields later), we did not include the "Values filtered by previous expressions" option - it is not the same list unique values that are dynamically populated, but rather a static list per users' choice. That's the reason why you do not see that option in your case.
... View more
01-17-2024
10:55 PM
|
1
|
0
|
4588
|
|
POST
|
Hi @BrittanyBurson Your issue above is different from what Hailey had. You have only one clause in the screenshot, telling me you used multiple filter items, with a single clause in each of them, like this: It won't work because there is only one expression existing for each, hence no previous expressions at all. (there is only one previous filter item) The "Values filtered by previous expressions" option does not necessarily need to be within a set, but all the information needs to be in one filter item (multiple clauses/clause sets inside one SQL Expression Builder) - that's the meaning of "previous expressions": See two individual clauses (not inside a set) that have that option as expected.
... View more
01-17-2024
10:51 PM
|
0
|
0
|
4588
|
|
POST
|
@Renata This is the expected behavior since these two widgets are using the same data source. If it doesn't change upon each other's change, then that would be a bug. If you do not want them to affect each other, you may opt to use two different data views, but I am not sure if that will achieve the purpose of filtering (by attributes vs. by time) of the same data if that's what you want to do. You can refer to more details about data usage in Experience Builder in https://doc.arcgis.com/en/experience-builder/latest/build-apps/select-data.htm
... View more
01-17-2024
10:08 PM
|
0
|
0
|
1378
|
|
POST
|
@LaurenLumHee The four date-specific operators will only be available in AGOL-hosted services. See details in the document https://doc.arcgis.com/en/experience-builder/latest/configure-widgets/filter-widget.htm#ESRI_SECTION1_068446E215E04DFD8ECC7AA272773BF3
... View more
01-16-2024
09:49 PM
|
0
|
1
|
1628
|
|
POST
|
Hi @MeganeDi_Nardo Units MGRS & USNG have been supported since the AGOL 2023 Mar release, which means they will be available in Enterprise version 11.2 and later - if that's your case.
... View more
01-14-2024
07:01 PM
|
1
|
1
|
2350
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 3 weeks ago | |
| 1 | 2 weeks ago | |
| 1 | 2 weeks ago | |
| 1 | 11-23-2025 06:08 PM | |
| 2 | 03-18-2026 01:07 AM |
| Online Status |
Offline
|
| Date Last Visited |
Wednesday
|