@ClayDonaldsonSWCA Currently the Add Data widget supports adding KML layer via URL. If you want to upload KMZ/KML files, you may submit an enhancement request.
@Jianxia - thanks. where would I put an enhancement request to update the add data widget to have the same features as the web-app builder version? Losing kml support and the curated filter very much limits the usefulness of the widget for my organization.
Thank you @Jianxia looking forward to batch updating. It would definitely create efficiencies and it seems there's a need for it in various organizations.
When can we expect the next update not that we are past Q1 2023?
I will clarify my request to open the Feature Info widget when clicking on a feature on the map.
I am trying to replicate the behavior of the Instant App Sidebar template, which will open the sidebar to the Feature Info tool when clicking on a feature, regardless of whether the Sidebar is collapsed or currently displaying another tool. I find the behavior of the sidebar in the Instant App very user friendly and seamless, and it would be great if ExB could replicate it. One of the great features of the Sidebar is it opens the widgets full height and not over the map, so the user does not need to resize or move the widget window.
In ExB, I am using the Sidebar Template and have added a Section widget to the Sidebar. Within the Section widget I have added 12 views, one for each Tool I wish to add. I have added a tool widget to each view, one of which is the Feature Info widget. I have added a column next to the Section with 12 buttons that open each of the views. I prefer the look of buttons to the Views Navigation widget. It will be very common for a user to have a widget open other than the Feature Info, such as Layers or Legend, or perhaps even have the Sidebar closed. Then they may click on a feature on the map, expecting to see a pop-up. But no pop-up info will be visible unless the user clicks on the Feature Info button. This in not intuitive for the user. I would like the view to switch to the Feature Info widget when clicking on a map feature, not matter what widget is currently active, or if the Sidebar is currently closed.
Attached is a screen shot of a feature selected on the map while the Draw widget is active - note that no data is displayed. Selected Feature; Draw active
Then a screen shot after I clicked on the Data button, which opens the Feature Info widget. MapFeature after activating FeatureInfo
Thank you for the updates included in this thread. As with many other users, I'm a bit worried that EB widgets might not inherit all of the features present in their WAB counterparts.
Can you tell us if there will be similar functionality in the new Select widget as is present in WAB? For example, one of the most useful features to our institution is the ability to quickly sum field values in a selection, in our case Area (sq. ft). In addition to the ability to control selected layers, this requires both the add/remove selection functionality (using the "Ctrl" and "Shift" keys) for selecting multiple non-adjacent features, as well as the "Statistics" tool for quickly calculating averages and totals of a field. If this is not already planned for the new "Select" widget, I desperately hope that it can be added. The vast majority of what we are planning to use ArcGIS for hinges on some of these specific and very useful features that are present in WAB.
Some widgets appear as if they are complete and available in the functionality matrix (Functionality Matrix for Web AppBuilder and Experi... - Esri Community) when there is actually a lot of missing functionality within each of the widgets. You've highlighted some of the key features like attribute statistics in the attribute table, and showing the count of selected features in the select widget. I hope that these standard widgets are going to be improved, as well as new/missing widgets being developed.
Are there any plans to fix the issue where the Form Title doesn't transfer over to the data editor from the map? At the moment it defaults to ID which is a bit annoying
You mentioned in a response above that there is no estimated timeline for group filtering. Is this because of technical issues or is it that other updates are higher priority?
Obviously everyone will argue that their own needs should be prioritised but this is a feature that's been requested in ArcGIS Ideas for 2 years now and the lack of it is meaning we can't use EB for a lot of our projects. Anything that uses related layers, which is a lot of our survey data from S123, is difficult to filter at the moment as you can't filter multiple layers based on a common field (unless you use multiple filters which looks terrible from a user experience). Is the prospect of adding additional layers to the filter or allowing filter actions to include the framework likely to be arriving this year?
Appreciate you get a lot of messages on here but any update on this would be very much appreciated.
Any idea when the Emergency Response Guide widget will be added to experience builder? It is currently only available in web appbuilder, which is not mobile friendly, and of course that is being retired next year.
are there any plans to enable the new Related Objects functionality in the Popups, in the Info Panels? So that we can build Info Panels that respect the Popup Arcade Expressions?
Hi @Jianxia is there any timeline for adding the ability to add text within the Draw widget please? I've raised this before and you said it would be added to the list, just wondering if there is any update. It's one of the main things stopping us migrating our larger WAB applications at the moment. Many thanks 🙂
@Jianxia Do you know if the Parcel Drafter is ever slated for development in experience builder? Any suggestions on how we might ask for it/request that it be added to the list?I think a lot of communities might find it handy. Any suggestions on something that may replace it?
We've spent a fair bit of time on and off over the last year with the online version of ExB trying to replicate a key AGO Dashboard that is in desperate need of update. There are several crucial features in our Dashboard that are missing in the ExB product that we need before we can convert to ExB. However, we need other functionality in ExB that doesn't (and probably never will) exist in Dashboard.
Basically, we're stuck and are unsure when we'll be unstuck.
These features (described below) have been missing from ExB since we started looking at ExB a year ago, and we're unsure when or if they'll ever be added to ExB. These are features that I have see other folks requesting on the ExB forums for a very long time. I opened ExB forum ideas on each of the needed features several quarters ago.
Can you give us a time line on when these features will be added to ExB? If you can't do that at this time, does that mean that these features will not be implemented within the next year?
Basically, we need to take a fork in the road on which platform we work from. I hate the idea of diving into the world of custom coding if the features we need in ExB will suddenly appear after we've spent the money to out-source writing the app in something like the Javascript API.
Here's what we need:
1. Utilize foreign keys/target fields in filtering data across layers. We have feature layers that we need to filter from another layer and also (separately) from pre-configured filters. We can do this in Dashboard as shown below, but there's no equivalent mechanism yet in ExB.
2. Summary table. This is also very important to us. We have thousands of features that need to be summarized in a table. Just showing the full table contents is not useful. This functionality exists in Dashboard as shown below, but is not yet in ExB.
3. Distinct count of a text field. Alongside the summary table, we use this to summarize our data. This is doable in Dashboard as shown below, but the Distinct (or equivalent) operator does not exist in the Dynamic Content menu for the ExB Text widget.
Please provide guidance. We can live with (but won't like) "not anytime soon", but we need to hear something so that we can make an informed decision on our development strategy.
Thanks,
Chip
PS:
As far as I can tell, the Developer version of ExB cannot easily be coded to handle the cross-widget interactions that we need in item #1 above (am I right in this?). I assume that we can code custom ExB widgets for items #2 and #3 below, but both of those custom widgets would themselves require outside help.
I'm glad to see the WAB Screening tool has been migrated to ExB as the NearMe tool. As @SarahNoakes1 mentioned in Jan 2023, NearMe appears to be lacking the "Report Settings" features of the Screening widget that allowed users to generate/print reports of overlapping feature attributes.
You mentioned some reporting features would be migrated "early 2024." Is that still the anticipated schedule for the Reporting features?
And will the Report Setting features be embedded as part of NearMe? (As it was within Screening widget settings.)
The reporting feature is a critical output of our workflow -- reports are the final product our users are expected to produce when using our app. Without it, we cannot yet migrate to ExB.
@JianxiaAre URL parameters still planned by the end of 2023? I'm retiring our WAB apps in September and after spending months building new apps in ExB, realized our URL passthroughs for various third party sites don't currently work. I've found workarounds but this is going to confuse a ton of people. This functionality should have been included awhile back.
Can anyone at Esri respond to the months' worth of questions and posts on this thread? As customers we don't appreciate the silence. We're told to post in this Community with questions and to engage with Esri teams, but then months go by with no responses. What's the point of this site if we don't get answers in a timely manner? There are questions going back to April - that's 6 months.
No entiendo porque algunos están cambiando todo lo que hay creado en WAB a ExB. Por lo mi experiencia ExB está todavía en muchos sentidos realmente atrasado con respecto a WAB y eso que WAB tiene bastantes bugs en según que widgets. Pero por ejemplo ExB está realmente atrasado con respecto a WAB podría poner varios casos como lo de que para hacer una búsqueda no se pueda filtrar por País y con la extensión del Mapa ya cambio tengas que hacer una vista de localizador en AGOL y ponerla pública para poderlo así mandar a mi Enterprise con lo que eso puede conllevar si alguien tiene la idea de hacer en vez de geobusqueda, geocodificación inversa o que por ejemplo no esté ni en todavía en la Matrix que ha puesto @Jianxia que aparece algo similar a selección del WAB que saca informes básicos pero sobre todo si el servicio es sincronizado saca una .gdb con Screening y solo esté planeado.
Así pasa con muchas herramientas. A ver el ExB está, uy bien a nivel gráfico y le idea es buena pero si tienes un Mercedes en la capa del coche pero el motor es de un Opel y da un montón de errores, porque no simplemente meten dentro del ExB los WAB que tengan y esperan a ver si ExB crece y soluciona los problemas.
O simple yo por lo pronto a no ser que sea algo muy estético sigo trabajando con WAB muchas veces porque con sus errores que los tiene será un Volkswagen de calidad baja pero tanto estéticamente como en el motor se porta igual.
A ExB le queda todavía un buen tiempo y pasa lo mismo con las Instant Apps que dan problemas en algunas platillas como la de adjuntos que luego le pones que se base en los adjuntos y en cuanto tiene 3 videos y 45 fotos se queda colgado el servicio .
@ClayDonaldsonSWCA , you may already know that adding KML files and using multiple curated filters have been added to the Add Data widget in the June release of ArcGIS Online. Thanks.
@HugoAlameda, Support for batch attributes editing is now planned for Q2 2024. This feature has a dependency on Maps SDK for JavaScript. We are working together to bring it into Experience Builder.
@TomDuncanGIS , Thanks for sharing. The design looks neat! Adding a default template similar to the Sidebar Instant apps or the Tab theme in Web AppBuilder is on the roadmap. As for displaying Feature Info in your case, unlike Instant apps, clicking a feature on the map could evoke other widgets like selecting a feature on the List widget or highlight it in the Table widget, therefore this is a little complicated. In the October release, we plan to add an option, allowing you to dock the pop up in a pre-defined position like top-center, top-left, or bottom-right, etc. When end users click a feature, the pop up will display in the position you configure in the Map widget. Will this meet your need?
Also, the Widget Controller adds a fixed option in the June release so you can display all widgets in a fixed panel size and position, similar to what WAB does.
@JDenham, thanks for sharing how the Select widget is used in your institution. The standalone Select widget in Experience Builder is targeting Q1 2024, allowing you to control selected layers. The Statistics capability will be a data action. If it does not make to the initial release, it will be added later. The ability to adding/removing features from selection using Shift or Ctrl keys will be available in the Select tool in the October release, then the standalone Select widget.
@williamsonsa_fultonhogan, understand your concerns. Yes, each widget has its own parity, such as Statistics in the table and select widgets. Once the Statistics data action is available, similar to Export, it will be added to widgets to which it applies. We prioritize widgets migration based on their main functions and usage and try to reach the parity through releases. We are currently working on the parity status chart in each widget and hopefully share with the community soon so you know what is planned or not planned for capabilities in each widget. Thank you for your feedback.
@AnthonyJonesRSK, the capability of Group Filter is planned for Q1 2024. It will be part of the Filter widget. You are right. It is a popular request in the community. Due to resources, other features like Geoprocessing widget have higher priority. Thanks for bringing it up.
@Cory_Williams, could you please specify "Related Objects functionality in the Popups? Do you mean show related records in the popups? Currently, it should show when you open the popup on the map in Experience Builder. The plan to show related records in the Feature Info widget is targeting the first half of 2024.
@malte, Unlike ArcGIS Enterprise, we don't support adding custom widgets in ArcGIS Online due to security concerns. However, we plan to enable you to purchase and add custom widgets listed in ArcGIS Marketplace from Esri Business Partners, similar to what you can do with Web AppBuilder hosted custom widgets in ArcGIS Marketplace. Currently no timeline yet.
@JamesShreeve , thanks for the follow up. Unfortunately this feature has a dependency on Maps SDK for JavaScript. We are working together to bring it over. Your request has been added to the backlog issue. Unfortunately there is no timeline yet.
@santamariaa, unfortunately the Parcel Drafter widget is not planned to be available in Experience Builder. See WAB and ExB functionality matrix. However, it is under the consideration of new Web Editor application from Esri. I would recommend contacting @ScottSandusky, who is the product manger for Web Editor, ask your account manager to help connect with him, or send email to me (jsong@esri.com) so I can connect you with him.
The count operator in the Dynamic Content menu should count unique values automatically when you choose a field other than object id as documented under Dynamic content->Statistic:
"Results can be the maximum, minimum, average, or sum value of a numeric field; the maximum or minimum of a date field; the feature count of the feature set (using the unique ID field); or if the service supports distinct count, the number of unique values for a field."
Could you give #2 ad #3 a try and see if they fit your requirements. Thanks!
@RyanBohan thanks for posting the request for ability to copy and paste expression in the community. It has been added to the backlog issue. Currently there is no timeline yet.
@DeanSzumylo , The reporting capability is currently planned for Q2 2024. However, it is too earlier to tell how it is going to be integrated into Experience Builder including the Near Me widget. We may have more information early next year. Thanks for letting us know how critical this feature is for your migration.
@Anonymous User thanks for sharing your feedback regarding how the product team should engage with the customers in the community.
Glad to know that you are migrating WAB apps. Agree, URL parameters related to the map like Center the map, Define the extent, or Query a feature, etc are critical to the migration. Unfortunately these URL parameters do not make to the October release of ArcGIS Online. The team is working hard to support them in Q1 2024. BTW, you may send your inquiry directly to the experience builder email alias (experiencebuilder@esri.com) or to me (jsong@esri.com) if you would like to get your question answered sooner. Thanks!
@JuanManuelCruzHerrera thank you for your feedback. You mentioned some Web AppBuilder capabilities, such as location search with the country code option, reverse geocoding, selection, and reporting, are still lacking in Experience Builder. As mentioned earlier, we prioritize widgets migration based on their main functions and usage and try to reach the parity through releases. We are currently working on the parity status chart in each widget and hopefully share with the community soon so you know what is planned or not planned for capabilities in each widget. For the country code and reverse geocoding support, it would be helpful if you could submit them to the ideas site or to Esri Support, helping us track the requests for prioritization. Thanks!
@Jianxia thank you so much for all your responses here, I can only imagine what an epic task that was! I know us ExB users can get a bit cranky over being kept informed on the latest updates but I think we're just keen to fully utilise ExB and it's some of these missing features that are preventing us fully embracing it.
Thanks to you and your team for all your efforts, I look forward to trying out the group widget next year.
@Jianxiathanks for the update. Slightly disappointing we have to wait another 6 months to maybe see this. Our primary use is passing an attribute to our main web app, such as a parcel id or address. So from multiple third-party systems, the user can automatically be zoomed to a parcel or address using that passthrough. That simple function would be appreciated sooner rather than later. Especially when the instant apps can do this already. My current workaround is to have separate instant apps for those third-party systems and then a link saying "go here for the full app". It has been a confusing few weeks for our users as now they are being taken to two different apps depending on what system they come from.
I guess it's my own fault for jumping the gun and migrating to ExB when it's still a year or two out from being production ready. Kind of hard to go backwards now. My other option is to try to just move everything to an instant app (as limited as they are) and put the ExB apps on the backburner until the end of 2024.
@AnthonyJonesRSK , there are still some work from the product side in terms of parity. Thanks for being patient and willing to give it a try. Though we strive to deliver the feature upon the roadmap , sometimes it could slip off the planned release cycle. We see your excitements and challenges through your feedback, which is inspirational to the team.
@Anonymous User, Thanks for sharing the challenges your are facing. You are right that app URL parameters support is critical to the migration and integration with other systems. Passing a parcel id and zooming to the parcel in your case is a commonly used workflow. During the research and development, the team started to realize this feature is far more complicated than its counterpart in Web AppBuilder due to the fact that data in Experience Builder could be many maps or without any maps. As a result, it is slipped to the next release cycle (Q1 2024) since much effort is needed to implement it holistically.
Thanks for willing to give it a shot and sharing your feedback. We should have spent more time engaging with the community. As mentioned in the above reply, it is inspirational for us to see your excitements and challenges through your feedback! As each widget also has its parity, we will continue working on migrating those capability in 2024. The end of 2024 should be a good time to re-evaluate ExB. Thanks!
Thanks @Jianxia for all the updates about the ExB road map.
Having the Filter widget support multiple layers (with shared attributes) is what I came to this page to see and very glad to hear it is coming. Now I just need to figure out what to do in the meantime.
Also, thanks for the new Near Me widget as that is something we needed. I do have two requests if I may:
1. The option to hide the Closest Address text. Our use case is in an oil field, so the nearest address is not relevant. A bonus option could be to use some other layer to grab the nearest feature, but not necessary for us. Mainly just want to hide the text, so hope that might be an easy one.
2. The old WAB Near Me tool had the option for an integrated search, in lieu of clicking a location on the map. Would be nice to have that option back.
@RyanCoodey, for #2, the pop up will support Data Action in the upcoming release in October, so you can click a feature location on the map as an input location in Near Me. For #1, add @AzizaParveen1 for comments.
Thank Jianxia for responding to the group filter question. I know a lot of us have been very eager to have this functionality added -- it's definitely been my biggest issue with ExB to date.
If anyone is curious, I've developed a workaround to filtering multiple datasets with a common field. You can use the list widget to essentially create buttons and then trigger a framework filter for each layer. It is a little buggy at times, but it works and is much more user friendly than the search widget.
Could we add improving the mobile layout on the roadmap? Anything I build in Exb either may be viewed on mobile or will be exclusively viewed on mobile.
For example, I would love if the mobile layout was reconfigured to support smaller map sizes. Currently a map must have a height of 465 pixels to see the locate button. Anything under 465 pixels and you can not use the locate button (it disappears)
I have an request about two different widgets. Can you provide information on when the widgets for the "Add data" and "Basemap gallery widget" will be available in Experience Builder on Enterprise?
@Cory_Williams, This is a known issue. We plan to address it in 2024. In fact, Experience Builder does not support for displaying related records in Feature info, Table, Query widgets, etc. It is one of the important capabilities that has not been migrated over. Your request has been added to it.
@ADev The ExB's map widget has an embedded measure tool. Though, you cannot configure it like you could in WAB. I just created this idea requesting the Ability to change the default units in measure widget. Since the Functionality Matrix for Web AppBuilder and Experience Builder show the measure widget as already implemented, I'm guessing your response from @Jianxia would be just that. This is why I made the specific idea about setting the measure tools units as opposed to simply asking for the same configurability as the measure tool in WAB. Most of the time our requests have to start small.
Will the new NearMe widget eventually have the functionality to display results, via an inputted layer file, like in the screenshot below?
I currently have a WAB that returns major districts from an inputted address and zoom to the address on a map. I want to replicate this in Experience Builder. Thanks.
