|
POST
|
Respectfully, one could argue that the Feature Info widget could and probably should at the least include a message or data action or a data source configuration setting that handles coincident features or allows , same as the 4.x popup. Otherwise, an out-of-the-box workaround like I posted above makes the users perform too many clicks to find the info they want. As an 'Experience' we all know that's not good. I well recall having to instantiate this behavior at 3.x with the Info Template, and we should be past that for non-developers.
... View more
08-27-2021
12:40 PM
|
3
|
1
|
7980
|
|
POST
|
Thanks for looking into this @Junshan_Liu . You should be able to access the application, it is fully public unless you have something on your end that is preventing you / blocking our ags3.scgov.net domain. (It its public, we are a county government) . Regardless, yes the layer works just fine in the Experience Builder Dev Edition 1.5 at design time / build time and I am glad you found the same. However, when 'downloading' the published app to zip, unzipping it to our web server, the published / built app at https://ags3.scgov.net/thorofareagol (...\inetpub\wwwroot\thorofareagol\cdn\0) cannot access some of the libraries, and the query widget does not function: So either the Dev Edition at 1.5 is not downloading / compiling the built app / query widget correctly, or I have another security issue with my web server or IIS. To me, if the layer is available to the layer list widget, it should not have an issue with the query widget. Thanks
... View more
08-27-2021
06:57 AM
|
0
|
3
|
5132
|
|
POST
|
I have been struggling some this myself. For now, I don't think there is an OOB solution, other than to maybe configure the query widget so that you only include a spatial selection. Then using the point tool, clicking a stacked parcel and then clicking 'apply' will select all the parcels in the stack. Of course, that's 2 steps for the user so it's not ideal. The results are then presented in the query widget return as a list. Otherwise, it looks like I have to use the developer edition. I found a video in the experience builder help videos from 2021 dev summit where the presenter does talk about tweaking the feature info widget by adding in the message action from the list widget that selects all the features in a stack: https://www.esri.com/videos/watch?videoid=5GRs0ubHESQ&title=Why%20We%20Used%20Experience%20Builder%20and%20How%20it%20Went%3A%20A%20Developers%20Story
... View more
08-26-2021
01:29 PM
|
1
|
0
|
7993
|
|
POST
|
Yes hello @Junshan_Liu . I am working with a simple hosted feature layer from Enterprise 10.9. In this application: https://ags3.scgov.net/thorofareagol the feature layer can be found here as an agol item: https://sarco.maps.arcgis.com/home/item.html?id=3f854ed4c2684ae89b3aa54c2c424c21 The layer does come from a referenced collaboration. I host my feature layers on our portal, and send to arcgis online in a distributed collaboration.
... View more
08-26-2021
10:30 AM
|
0
|
5
|
5151
|
|
POST
|
As a follow-up and as a test for whether or not anonymous access has an effect on this issue, I registered the 1.5 Exb with our ArcGIS Online organization. I created a simple jewelry box theme app with one layer and one query. As I noted earlier, while the data source is available to the map, mapview, layerlist and legend, the load fails for the Query Widget. I am beginning to suspect an issue with the 1.5 version, as I receive the same load module errors. Maybe some of the modules are being compiled once I download the zip. I don't know. Everything works in EB Dev, it only fails once deployed to my standard IIS webserver here is a link to try for yourselves: https://ags3.scgov.net/thorofareagol @DavidMartinez @jcarlson
... View more
08-25-2021
12:49 PM
|
0
|
2
|
5284
|
|
POST
|
Hi - does anyone know why a source layer selected from your experience builder developer 1.5 edition map would not be available to the query widget, when the same layer is available to the layer list widget? I have an source webmap built from/in map viewer beta on in our 10.9 portal. The layers and webmap are all public. The layers are all available to the layer list widget, and so when I deploy the app to my webserver, I do see all the layers. BUT, a Street layer for Query Widget, selected from the map as the data source, is NOT available to the query widget. I get a whole host of jimu errors when I open the query widget: This could not be a more simple deployment. I'm just trying to get some simple things resolved before trying to add in custom widgets and code. It shouldn't even require a client id because everything is public. @DavidMartinez perhaps you have seen this??
... View more
08-25-2021
12:44 PM
|
0
|
10
|
5887
|
|
POST
|
Hi - does anyone know where I can get at the output graphic from a 'Show on map' message for the Query Widget in Experience Builder Dev 1.5? Thanks - David
... View more
08-23-2021
07:50 AM
|
0
|
0
|
707
|
|
POST
|
Thanks for the reply, that's what I thought too... I do not have a custom widget included yet, but was having trouble with the OOB Query widget, which is not displaying any of it's form elements. As if it can't read from the source layer, even though the source is the webmap, and all layers are public. The Layerlist widget does display the same layer I am trying to query. I did try copying the package into the download - all that did was then make the deployed app prompt for my portal credentials. The oob query widget issue is a separate question, so I'll re-post that issue if I can't resolve....
... View more
08-20-2021
07:05 AM
|
0
|
1
|
2589
|
|
POST
|
@AndyWells In working with Dev edition 1.5 query widget my zoom-to message action for query results does seem to work in development for my State Plane layer. However, when I downloaded and unzipped my solution to my web server, the query widget does not display any of it's elements - it's just a blank white box. Not sure what I'm doing wrong here. maybe something to do with the re-direct uri's - even though everything is public (although the portal does not allow anonymous access) @DavidMartinez
... View more
08-18-2021
12:04 PM
|
0
|
1
|
9195
|
|
POST
|
HI - Seems like this is still an issue, at least for Enterprise. I am working in the Developer Version 1.5 · July 2021 release. I registered my developer version with Enterprise Portal (10.9). My portals' custom basemap group (gallery) is public, as are the webmaps and any custom vector tile layers the group contains. Like most org, anonymous access to the portal is disabled. My guess is this the problem - no anonymous access. Either that or it's something with how Living Atlas layers are shared?
... View more
08-18-2021
11:55 AM
|
2
|
3
|
4591
|
|
POST
|
Hi - in downloading and deploying my 1.5 version experience to my webserver, the app console log is showing that its missing the jimu-for-builder module. For builds that are constructed from a portal-registered EB 1.5 dev environment is this normal? Should the jimu-for-builder module be part of the zipped download? Thanks- David
... View more
08-18-2021
11:39 AM
|
1
|
3
|
2616
|
|
BLOG
|
Hi Robert - getting back into it. Re-acquainting my self with the api ta 4.x, the jimu and now the react framework. To be honest, what I"ve done so far is take on the tic-tac-toe React tutorial to gain a better understanding of state. As I'm late to the conversation you're probably way ahead. For me (and perhaps others from the WAB dev edition) there are benefits in both approaches, right? On the one hand, those of us from the wab dev are used to working with the various config files and modifying js/ts/css files directly / as-required. On the other, you releasing fully configurable with the UI lets / enables us to ride (benefit?) on what you've done and hopefully learn / gain a better understanding of the development pattern for the EB. You've probably already thought about creating maybe an early release to be followed by a fully configured release? Sadly though, because I don't yet understand the full pattern, I can't say if that's a realistic option..... my 2 cents. In the meantime though, here is something I have configured totally out of the box (and online hosted at this time). The idea was to take planning data (that is almost always 'themed') and instead of stacking layers in a toc or layer list, split up the app into focused map themes and take full advantage of the List Widget for sorting and querying. The idea being that, for planning-type data such as zoning and land use, most users are just looking to see what / within their address or property lies. Each map page is a modified sidebar, and each layout is custom for seamless (hopefully) I added as much intelligence as I could into focus layer itself, and map actions for certain maps to zoom to same extent. The home page functions as an intro-style gallery page. Thanks, David
... View more
08-12-2021
12:31 PM
|
1
|
0
|
9076
|
|
POST
|
Yes, I have nothing new to add to this. ArcGIS Online Hosted feature layers do not throw an error, layers accessed in arcgis online by reference (either from a collaboration or when accessed by 'add item' and providing a service url) do.
... View more
08-12-2021
06:55 AM
|
1
|
0
|
4622
|
|
POST
|
no it doesn't, not like a file gdb or an enterprise rdbms can store a blob or raster data type. Like when you create a tile cache for a hosted feature layer, that tile cache is going to reside in the cache directories, not in the relational datastore. At least that's my understanding.... For imagery, we use the image server role on our federated site. The source imagery resides in an enterprise file share, like a san, and the mosaic datasets that source the image services reside in a file gdb on the federated sites' data-store directory
... View more
08-11-2021
11:00 AM
|
0
|
0
|
2461
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 07-01-2026 05:41 AM | |
| 1 | 06-26-2026 12:39 PM | |
| 6 | 06-25-2026 07:23 AM | |
| 1 | 06-17-2026 06:04 AM | |
| 1 | 06-08-2026 08:37 AM |
| Online Status |
Offline
|
| Date Last Visited |
12 hours ago
|