POST
|
@gis_KIWI4 , at first glance it's hard to tell. Please reach out to me via email avezina@esri.com and we can set up a meeting with a screen share to look into it.
... View more
a week ago
|
0
|
0
|
53
|
IDEA
|
@KevinN_CSJ @MoyaCalvert_01 Thank you for the feedback. We are working on the new functionality for copy-paste and are taking this into consideration.
... View more
2 weeks ago
|
0
|
0
|
45
|
BLOG
|
@JCooley_ClackamasSWCD Regarding your question: "I don't want to automatically overwrite the date field when I'm editing another field. Is there any workaround that allows conditional statements to be used in the calculation code?" Yes, you can use the $editcontext.editType Profile Variable to determine if the value is calculated only on create or update. Form Calculation | ArcGIS Arcade | ArcGIS Developers Some application examples in here: Go Beyond the Smart Editor using Smart Forms (esri.com)
... View more
2 weeks ago
|
1
|
0
|
166
|
POST
|
Thank you @gis_KIWI4 , I looked into the BUG report. Message actions are not supported for the Utility Network Trace widget as of Enterprise 11.1 or 11.2. You will notice there aren't any Actions that can be configured from this widget. Message actions are a widget-to-widget configuration and must be configured in the Utility Network Trace widget to observe the expected behavior you have described. In other words, since the "records selection change" trigger is being performed by the Utility Network Trace widget when you run a trace, the Utility Network Trace widget is where the whole action needs to be configured. Message actions will be available for the Utility Network Trace widget as of 11.3 (and are available right now in the ArcGIS Online version of Experience Builder). See this blog for hybrid setup: Configure an Application to Trace a Utility Network (esri.com) (see step 3)
... View more
3 weeks ago
|
1
|
2
|
79
|
POST
|
There were some limitations from the SDK side that have now been lifted, and adding support for the Forms in the Attributes-only mode is now possible but requires refactoring of the Edit widget. This is on the roadmap for an upcoming release.
... View more
3 weeks ago
|
0
|
0
|
134
|
POST
|
Hi @FranklinAlexander , this is a known limitation right now. The Forms you configured will not come through in the Experience Builder Edit widget when you use Attributes only mode, but it should work as expected if you use Geometry & Attributes when configuring the Edit widget.
... View more
4 weeks ago
|
0
|
2
|
198
|
IDEA
|
@LindsayRaabe_FPCWA , Thank you for the details, and nicely done getting to the bottom of this one! Yes, a default value needs to be set for the switch to display as expected. If the default value was not defined when the field was created, it is possible to do it from the Templates. Authoring and managing Templates is not yet supported from within the Map Viewer, but it is planned for an upcoming release. Once it's implemented, hopefully this workflow will be more straightforward.
... View more
a month ago
|
0
|
0
|
145
|
IDEA
|
Hi @LindsayRaabe_FPCWA , I am not able to observe the issues you've described both for Experience Builder or Field Maps. Experience Builder (in ArcGIS Online) Field Maps Is there any further information you are able to share? Is anything different with your setup?
... View more
a month ago
|
0
|
0
|
174
|
POST
|
@DNVT There may be limitations on what functionality is available to you based on your Enterprise version. Related records in the Map Viewer popup, the Forms and the Editor were added at 11.2.
... View more
a month ago
|
0
|
0
|
250
|
IDEA
|
@DebHSF Thank you for your post! Yes, I understand and agree that this workaround is not ideal and that a schema change is most definitely not preferred, and we're looking into providing better options for this workflow for the future.
... View more
a month ago
|
0
|
0
|
184
|
BLOG
|
@WetherbeeDorshow Thanks for letting me know, please try accessing again now.
... View more
a month ago
|
0
|
0
|
530
|
POST
|
Please also see this post for proposed workaround: How to override values for fields with calculated expressions (esri.com)
... View more
a month ago
|
1
|
0
|
116
|
IDEA
|
Please see this proposed workaround: How to override values for fields with calculated expressions (esri.com)
... View more
a month ago
|
0
|
0
|
152
|
BLOG
|
You can save time collecting data and automatically calculate attribute values using the Editor widget with "smart" Forms. The Editor widget is available in Map Viewer and app builders such as Experience Builder and Instant Apps. The Forms builder is available in Map Viewer and Field Maps Designer; all you need is an editable feature layer. If this is your first time, read this blog to get started building Forms. Challenge The values for fields with calculated expressions cannot be edited or recalculated on demand, while editable fields do not support calculated expressions. Common use cases for the need to override a calculated value: When the calculated expression fetches values from intersecting features: if multiple features are intersected, an unexpected value can be returned which needs correcting. Calculated values based on other field values: if the other values are incorrect, manual adjustments may be required. When the calculated expression doesn't return any value (blank/null): users may need to enter a value manually. Workaround Leverage field Logic in Forms to set dynamic behavior for editability based on a condition. Open this sample Feature Layer in Map Viewer to view an example. In the provided example, an editable feature layer has a Current Date field for which the value is automatically calculated based on the current date and time. Another field is used to define conditional editability for the Current Date field. If the Current Date field is editable, the date value can be changed. If the Current Date field is not editable, the date value is calculated and cannot be changed. Follow the steps below to incorporate this field Logic into your editable layers. Step 1 - Update your data schema Note: This workaround may impact your data model as you may need to add a new field to your layer. For a new editable layer or an existing layer, add a new field of type String. Give the field a name (e.g. Change Date in the sample layer) The field must be Editable The default value for the field should be "No" Add a List of Values (domain) for the field. Values should be "Yes" and "No" Step 2 - Add the calculated field to the Form In Map Viewer or the Field Maps Designer app, create a Form for the layer. To the Form, add the field for which a value needs to be calculated (e.g. Current Date in the sample layer). Under Logic, define the Calculated expression using Arcade. In the example below, the expression Now() will automatically populate the current date and time into the Current Date field. Step 3 - Add the conditional field to the Form To the Form, add the field that end-users will use to make the Current Date field editable (Change Date in the sample layer). Under Formatting, update the Display name for the field (e.g. Toggle to override the date value above) Change the Input type to Switch. Step 4 - Add Logic for the calculated field For the calculated field (Current Date), under Logic, check the box for Editable and configure a new expression. (e.g. the Current Date field becomes editable if the Change Date field value is "Yes") Optionally, add an expression to make the field required if it's blank. __________________ Special thanks to @ChrisFox, @DougMorgenthaler and the Field Maps team for sharing this approach. You might also like From the Smart Editor to Smart Forms (esri.com) Go Beyond the Smart Editor using Smart Forms (esri.com) Common calculated expressions for ArcGIS Field Maps (esri.com) Use the filtered value as a default field value - Esri Community
... View more
a month ago
|
8
|
10
|
875
|
Title | Kudos | Posted |
---|---|---|
1 | 2 weeks ago | |
1 | 3 weeks ago | |
1 | a month ago | |
1 | a month ago | |
8 | a month ago |
Online Status |
Offline
|
Date Last Visited |
yesterday
|