|
POST
|
This issue was resolved on a call. Documenting the details here in case someone else experiences this: The layer was created with string values already available for this field, and the coded domains were created and assigned to this field after the fact. The issue was caused by an ensuing mismatch between the values present in the field and the valid values for a coded domain that the field now expects. For example, the value found in the field is the string "Non-Lead", which was typed as such into the field, but the valid coded domain value for Non-Lead is the code "3". The Editor widget then identifies this value as an additional value that does not belong to this coded domain. The user can use ArcGIS Pro to easily resolve this issue. Bring in the problematic published feature service into ArcGIS Pro Use the Select by Attributes tool to select all features where UB_Utility_Side = "Non-Lead". Open the Calculate Field tool, and using Arcade as the scripting language, calculate UB_Utility_Side = "3". Once this is calculated, the value "3" will now be written into the database, while the domain value description "Non-Lead" will be visible in the row. In the Editor widget, you should then only see the domain values as available value options.
... View more
12-08-2023
10:36 AM
|
2
|
0
|
3053
|
|
POST
|
Hi @PaulDoherty2 , The Group Layer item type is not yet supported as a data source in Experience Builder but is on the roadmap. We'll keep you posted with any updates.
... View more
12-08-2023
09:38 AM
|
0
|
0
|
2336
|
|
POST
|
Hi @azainomv , A few questions, and just to help us narrow down the source of the issue - please could you test doing the same edits from within the Map Viewer Editor widget? Are you seeing the same behavior? Were you able to log a Bug report with Support? Did they provide a case or bug number? Otherwise, any chance you can share your layers and map with us? You can connect with me directly at [email protected]. Otherwise, if you were able to recreate a small subset of your data in ArcGIS Online (you could publish the layer with your schema with some dummy features just as an example) and share it with us, that would be helpful so we can take a closer look. Thank you!
... View more
12-07-2023
07:32 AM
|
1
|
1
|
3137
|
|
POST
|
@AliciaSabatino Thanks for clarifying. Your request is similar to this one: In Experience Builder, can a hosted feature layer ... - Esri Community. Unfortunately, this is not supported in Experience Builder yet, but you may find a workaround using Survey123 and caching answers as described here.
... View more
12-06-2023
03:50 PM
|
0
|
1
|
1898
|
|
POST
|
Hi @ScottHansen__MDP_ , that is not currently supported in the Experience Builder Edit widget, but a valid request as this is supported in the Web AppBuilder Smart Editor widget (to be retired at the end of 2025). Thank you for posting this question. One option you may have would be to create a Survey123 using the web designer and leverage the cache option for answers. Web designer essentials—ArcGIS Survey123 | Documentation Technically, you should then be able to use the Survey widget in Experience Builder to expose that survey within your app for editing.
... View more
12-06-2023
01:50 PM
|
0
|
0
|
1583
|
|
POST
|
The Batch Attribute Editor widget only supports batch editing attributes, not geometries. Right now it seems the only client that supports your workflow is ArcGIS Pro.
... View more
12-06-2023
12:58 PM
|
1
|
0
|
4736
|
|
POST
|
Hi @EricRuberson1, you can create your own Editor widget user interface. The default Experience Builder Edit widget comes from the JavaScript Editor, which is built around EditorViewModel. You should be able to customize an interface using the different JS Editor classes and then wrap it into a custom Experience Builder widget. There are also a lot of widgets within the ArcGIS Maps SDK for JavaScript itself that you could leverage out of the box, so at this point, you could potentially also consider building a custom app using the Maps SDK for JavaScript and perhaps leverage Calcite Design System for the user interface. All options will present some challenges but are feasible. An aside - the JS team is working on refactoring the Editor widget for the coming releases which may componentize the different pieces of the Editor and make it easier for you to bring them together in a more custom UI.
... View more
12-05-2023
07:46 AM
|
1
|
0
|
1053
|
|
POST
|
Thanks for sharing @YS2388. I'll touch base with the team on this one and get back to you.
... View more
12-01-2023
12:02 PM
|
0
|
0
|
1563
|
|
POST
|
@YS2388 , Please are you able to share a screenshot for " For the smart form, the Edit widget respects the fields configuration and any group names, however, the form's title is entirely not displayed and instead the "Display Field" appears." showing what you are seeing and what you'd expected to see?
... View more
12-01-2023
10:51 AM
|
0
|
4
|
3154
|
|
POST
|
Hi @EricaCirigliano , These drawing options are still missing from the editor but are on the roadmap. You are correct, there is not yet full parity with all the functionality Smart Editor provides. We'll provide a more detailed parity matrix soon.
... View more
12-01-2023
10:32 AM
|
0
|
1
|
4446
|
|
POST
|
If you are only looking to update attributes for a feature layer that has a smart form configured and is found in a web map, the smart form should show up as expected when you edit those features. Two things to consider: 1. Make sure to connect the Edit widget to the feature layer that is found in the web map data source. That will be important if you have created the smart form from within the web map and it has not been saved against the feature layer. 2. If you are connecting the Edit widget directly to the layer itself, you should go to Map Viewer, and from that layer's properties, you'll want to hit Save. This will save, against the feature layer itself, any changes you've made to this layer from within the web map (such as symbology and the smart form).
... View more
11-30-2023
09:56 AM
|
1
|
6
|
3163
|
|
POST
|
@YS2388 Thanks for clarifying! Yes, the "Attribute Only" case in the Experience Builder Edit widget may behave differently. In this case, are you editing a Table layer that has a smart form configured?
... View more
11-30-2023
09:32 AM
|
0
|
8
|
3167
|
|
IDEA
|
While the Web AppBuilder Smart Editor widget "as-is" will not be migrated to Experience Builder, the functionality you are requesting will be provided over time through the new Editor widget, and possibly some more related tools. Multiple teams at Esri are collaborating right now and are fully dedicated to making this possible. We apologize that this is taking some time.
... View more
11-30-2023
08:16 AM
|
0
|
0
|
3961
|
|
POST
|
Hi @taylorrobinfemadhsgovRobin , if you try making these same edits and adding the attachment using the Editor widget directly within the web map (using the new Map Viewer), are you also seeing this issue?
... View more
11-30-2023
07:58 AM
|
0
|
0
|
2000
|
|
POST
|
The Smart Editor widget "as-is" is not being migrated to Experience Builder. Functionality you are requesting will be provided over time through the new Editor widget, and possibly some more related tools; multiple teams at Esri are collaborating right now and fully dedicated to making this possible. We apologize that this is taking some time.
... View more
11-30-2023
07:56 AM
|
2
|
2
|
2451
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | a week ago | |
| 1 | 01-08-2026 09:58 AM | |
| 5 | 03-31-2026 01:39 PM | |
| 4 | 03-03-2026 10:00 AM | |
| 1 | 12-05-2025 11:10 AM |
| Online Status |
Online
|
| Date Last Visited |
Wednesday
|