POST
|
@JanetSilb_Spike There isn't a way to configure these options in the widget right now. You may be able to leverage the Dev edition to customize this. Note that this widget leverages the ElevationProfileViewModel | API Reference | ArcGIS Maps SDK for JavaScript 4.29 | ArcGIS Developers
... View more
06-25-2024
08:08 AM
|
0
|
0
|
139
|
BLOG
|
@DavidMcCorkindale1 There is a URL parameter available for setting the version. When you add the Branch Version Managment widget and switch versions, you'll see the version update in the URL. See: Change the geodatabase version of a data source | Documentation You'll find documentation regarding the URL parameter to filter data sources here: Filter data sources | Documentation These are separate paramaters.
... View more
06-24-2024
07:18 AM
|
0
|
0
|
745
|
BLOG
|
Hi @WetherbeeDorshow ! Apologies, I am not sure if I understand the question. Please would you be able to explain into more details and perhaps illustrate how your data is setup and how you'd like it to work? Thank you!
... View more
06-22-2024
11:31 AM
|
0
|
0
|
89
|
POST
|
Hi @Heberlyeng, Have you looked into Hosted feature layer views? These will allow you to generate different views of your master layer and filter out any data and fields each workgroup should and should not see. You can then configure the symbology and Forms to customize the editing experience for every layer. I created a very basic sample to illustrate how this could work: Here's the master Hosted feature layer for the data from all workgroups: All Workgroups (arcgis.com) Here's a View for workgroup 1, created from the master layer above: Workgroup 1 View (arcgis.com) Here's another View for workgroup 2, also created from the master layer: Workgroup 2 View (arcgis.com) Here's the web map with the two workgroup layer views: Map with Workgroups 1 & 2 (arcgis.com) Here's an Experience Buidler app using the map above, but only showing the layer view for workgroup 1, as an example: Workgroup 1 (arcgis.com) Notes: When you create the Views for each layers belonging tor each of your workgroups, filter the data based on your workgroup domain values, and hide any fields not associated to the current workgroup for the view. Make sure to enable editing on your Hosted feature layer views; they are not editable by default when you create them. You’ll want to author the editing Feature templates for your View layers. Right now, the easiest way to achieve this for will be using the Field Maps Designer application. (Not intuitive, I know – this functionality will be available in Map Viewer soon) In Experience Builder, when you add a web map as a data source, you can choose which layers from the map are available. I hope this helps! Let me know if you have any further questions regarding how this was setup.
... View more
06-22-2024
11:25 AM
|
0
|
1
|
229
|
BLOG
|
@WetherbeeDorshow Apologies, should be accessible now!
... View more
06-18-2024
11:04 AM
|
1
|
0
|
677
|
BLOG
|
Hi @WetherbeeDorshow, This took some playing around and picking some smart people's brains, but I think I have a solution that works and gets around the issue outlined by @LindsayRaabe_FPCWA above. Here's a sample web map that includes an example with the solution applied: View Sample You can save a copy of that web map to your Content and explore the Form and the way I configured the expressions. Here's the Calculated expression for the Current Date field: The logic for setting the Current Date as editable based on the Change Date field value is the same as described in the current blog post.
... View more
06-14-2024
04:11 PM
|
3
|
0
|
742
|
POST
|
Hi @AngelaEngland1 Please see this relayed topic: Solved: Re: 'Edit' widget ignores capabilities - Esri Community Keep in mind that while you may be configuring the apps for specific editing privileges, if you own the layer or are an admin, you may still be able to perform those edits yourself but your end-users should be restricted to they own user type/role privileges.
... View more
05-31-2024
10:03 AM
|
0
|
2
|
328
|
POST
|
Hi @ChristopherDawe Firstly, I'd recommend logging an ArcGIS Idea for your session variables request, if none already exist. Now, there may be some creative ways to come up with a solution for this. One option, and potentially the simplest, could be to leverage Survey123 and "Favorite" answers, so users can re-use answers when the users fill out the next form. Depending on your workflow, you can use Survey123 on its own, or an application like Experience Builder integrates easily with Survey123 so you can create a single application experience for your workflow. Another option may be using Calculated expressions in Forms. Here's a blog with a somewhat similar workflow: Use the filtered value as a default field value - Esri Community And here's a blog with some examples of Calculated expressions in Forms and how to set them up: Go Beyond the Smart Editor using Smart Forms (esri.com) I don't have all the details of your workflow, but my thought is that you may be able to leverage Calculated expression to automatically populate values for features you are creating based on the values in an existing feature in a reference layer you're filtering. Once you've setup your layers and Forms in the map, you could use Experience Builder (ExB) and create an application that goes as such: 1. First the user can create a new feature in a reference feature layer where those "session variable" values are stored 2. You could then provide an option for the user to select/filter only for the feature they have just created 3. Your calculated expressions are built as such that only the values from the remaining feature they've created in step 1 and filtered in step 2 will be populated in all the new features they create next I think for this to work well, it would rely on authoring a friendly user experience. One more insight; we are currently working on Copy and Paste functionality for the new Web Editor application, which will be released this coming June 2024. You'll be able to quickly copy and paste features with their attributes, which will prevent having to type all the values again. I hope any of this helps with waht you are trying to achieve.
... View more
05-30-2024
02:01 PM
|
1
|
0
|
267
|
POST
|
You have the privilege to edit the data because you are an admin/own the layer. If you log in as another user without admin privileges and try to edit the data using the published application, you'll see that they cannot edit the data. See: What's new—ArcGIS Experience Builder | Documentation
... View more
05-28-2024
02:23 PM
|
1
|
1
|
312
|
IDEA
|
WIth the upcoming June update, you'll be able to export the profile line to your Content with the attached profile statistics. This will create a feature collection item that you can then publish as a hosted feature layer. The elevation and distance values along the line can still be exported separately as CSV using the Export functionality in the Elevation Profile widget. For the ability to upload/add a line feature and get an elevation profile for the line, we're looking into supporting this in the following update before the end of this year.
... View more
05-28-2024
01:08 PM
|
0
|
0
|
360
|
POST
|
You'll be able to hide the Settings dropdown and the Filter types search box with the upcoming June update of Experience Builder:
... View more
05-22-2024
10:06 AM
|
1
|
1
|
133
|
POST
|
Copy-paste is planned to be supported in the new Web Editor application being released in the coming June update of ArcGIS Online. This will allow you to copy-paste your parcels into a separate layer. You'll need to make sure the target layer you are pasting into already has the necessary fields the ROW team will need to fill out. Also, you'll want all the field names and field types to match exactly between the two layers if you want parcel attributes to be also copied over. Once Web Editor is available, embed it within Experience Builder using the Embed widget. Then, use a widget that supports Data actions in Experience Builder to Export the data of selected parcels to CSV.
... View more
05-17-2024
01:32 PM
|
2
|
3
|
391
|
POST
|
Hi @Amanda__Huber , I am not sure I fully understand all the details of your implementation described above, but I'll give it a try. The toggle itself is not necessary. The bigger idea is that a field can become editable based on a condition expression. For example, you could have calculated expressions set for all the fields above the Observation Period field. These could be calculated automatically at all time. Then, you could also add an Editable condition to these fields as well, so that they will become editable if the Observation period value selected is Observation 1. This means if the Observation period selected is 2 or 3, the fields remain calculated and uneditable, but if the user chose Observation 1, then they become editable. I hope that makes sense.
... View more
05-14-2024
01:42 PM
|
2
|
0
|
363
|
BLOG
|
@DavidMcCorkindale1 Please could you elaborate on how you are using the version in a filter in your post? Thank you!
... View more
05-14-2024
07:07 AM
|
0
|
0
|
1364
|
IDEA
|
@edward33 Please would you be able to share an example how this information is being used? What's your use case and workflow?
... View more
05-08-2024
09:34 AM
|
0
|
0
|
329
|
Title | Kudos | Posted |
---|---|---|
1 | 17 hours ago | |
1 | Monday | |
1 | 2 weeks ago | |
1 | 3 weeks ago | |
1 | 3 weeks ago |
Online Status |
Offline
|
Date Last Visited |
9 hours ago
|