Latest Contributions by AlixVezina

Hi @West-d-gis , setting up the actions in reverse should also work in Experience Builder > with the selected related record filtering features from the parent layer!     ... View more

Hi @MariaNuñezReyes , Which version of Enterprise and/or Experience Builder developer edition are you using. If you have a fairly recent version, you should be able to leverage the export data action within Experience Builder to extract features selected by the Trace widget. Is this something you've already explored? ... View more

@ConorFlynn  Instead of multiple maps/apps, I think we could also add multiple view layers on the same map to allow configuring different forms. Yes, I think that could work too!! Let us know how you go! 😊 ... View more

Hi @ConorFlynn, I think providing field customizations for Batch editing at the widget level is under consideration. The recommended approach for customizing your editing experience remains to configure editing Forms for your editable layers. See: Configure forms for attribute editing (Map Viewer)—ArcGIS Online Help | Documentation Since it is possible to create different Forms for a same layer in different maps, I suggest creating a map tailored to your Batch editing workflows and customizing a Form for batch editing. Just a quick example to illustrate what I mean:       ... View more

Hi @West-d-gis , Related data is recognized within the Experience Builder data sources. When you configure Message actions between widgets, you can set Filter records. For example with the configuration below, when a Tree feature will be selected, it's related table records will also be selected. This is available in ArcGIS Online and starting at Enteprise 11.4. ... View more

@Amanda__Huber , "Allow you to also batch edit from feature layers and also table layer that are added to your app but not necessarily also in your map." When configuring the Edit widget, you will find two modes are available: Interact with a Map widget - the Edit widget will only read the feature layers from the maps in a Map widget for editing. This is similar to what was available in the Batch Attribute Editor widget in Web AppBuilder, where a map was always required in your app for the widgets to work. This newly introduced batch editing option in the Edit widget allows editing the feature's attributes and also their geometries. This was the main workflow the Experience Builder team was focused on supporting for batch editing in this initial release of the functionality. Attribute only - you can connect the Edit widget to any editable layers in your app, may they be in a map or not. This option only allows you to edit the attributes for features (in a feature layer) and records (in a table layer) - it does not allow you to edit geometries in the map. Technically, with this option, you could build an app with only a Table and the Edit widget and no map at all (example below). This is a new type of workflow that we did not previously support in Web AppBuilder. The team will add support for batch editing in this case too, in a future release, so you'll get the new ability to also batch edit records from a table layer. I hope this all makes sense! 😊   ... View more

Hi @Tiff , Select by attributes functionality is available via the Select widget. As far as I am aware, there aren't any plans to introduce select by attributes within the Edit widget itself and it will remain a workflow outside of the Edit widget as part of the Select widget. If you have any enhancement requests for the Select widget itself, please let us know!   For your second suggestion, I think a "Select all" data action in the Table widget is a great idea. I'll see if this is something the team has on their radar! ... View more

Hi all, For attribute only editing, you still have the ability to customize the editing capabilities for each layer in the map. Make sure you only allow for Update records > Attribute in the layer's capabilities. Example below:   In Web AppBuilder, the Batch Attribute Editing widget only supported being connected to editable feature layers from your map and did not support editing records from standalone layers and table layers.  Once implemented, support for batch editing in the "Attribute only" mode is an enhancement in Experience Builder that will allow you to also batch edit from feature layers and also table layer that are added to your app but not necessarily also in your map. ... View more

@ConorFlynn Thank you for pointing this out. Unfortunately, there isn't a "Partially implemented" status option we can use. 😔 The team is working on also supporting Attribute only mode and we'll keep you all posted once we have a clear timeline for it. ... View more

@SanjanaMali1 Unfortunately, I dont think that option is available other than in Pro or using custom code in the Maps SDK for JavaScript of Experience Builder developer edition. I'd recommend creating a new ArcGIS Idea within the community of the product where you'd like to implement this functionality. ... View more

@RodWoodford Thanks for specifying which version of Experience Builder you are using. This issue exists in the developer edition version 1.17, but it will be fixed in 1.18. If you are able to upgrade your apps to 1.18 once the version is released that should resolve the issue. 1.18 is planned to be released around July 23rd. ... View more

@AnnaHradecká After some discussions with the team, I learned that when multiple message actions filter the same data, the filters are "and" (added) together. So this is expected behavior, but we'll need to further evaluate this use case. It appears there may also be a bug when clicking between the two lists and clearing the selections in the lists. The team will investigate this further and see if it can be fixed with the next update this fall.   Workaround A potential workaround in your case may be to add the same data sources your app more than once and creating separate data views in each layer. Then you can setup actions to make sure these layers also "speak" to the map layers. For e.g., if you add the Feature Layer directly to your app's data sources twice: Then create distinct data views within each separate data source for your table layer:   The you'll need to setup the filter records message action in the List widgets to filter the data from the map. But instead of being able to use the data's relationship to trigger the action, you'll need to use fields (assuming I did this correctly below...) I hope this all makes sense.           ... View more

@RodWoodford I've been testing this on my end and cannot seem to reproduce the issue where the Edit widget does not de-activate. Please, would you be able to send some screenshots or a recording of the behavior in your app? Thanks! ... View more