POST
|
Stuck again! I'm really struggling to see how you are able to populate the FeatureForm associated with the Editor widget!? If I understand the example you linked correctly, it essentially creates the feature immediately and applies the attributes to "in the background". It then immediate loads the FeatureForm for the newly created feature, giving the user the opportunity to edit the default attributes. It is not really "pre-populating" fields before the feature is created but rather assigning values to the fields straightaway. I don't see how this can be achieved with the Editor Widget. When adding a feature using the editor widget the user must fill out the fields and press the "Apply" button before the feature is created. Therefore we can't assign attributes to a feature before it is created so I don't see how the fields can be "pre-populated" in this case.
... View more
10-07-2020
03:45 PM
|
2
|
0
|
1221
|
POST
|
Never mind. Realized I can use the "activeWorkflow" property to achieve the same end. As below, I can use a double-click listener event on the map view (similar to what you have done above) to listen for a double-click event that happens when a user finishes creating a feature. Then I can check the activeWorkflow.started property to determine that my double click is actually from finishing creating a feature (rather than the user just randomly double clicking on the map). I should be able to jump in here and assign my attributes here hopefully. view.on("double-click", function(event){
console.log("double-click detected");
if(editor.activeWorkflow != null && editor.activeWorkflow.started == true) {
console.log(editor.activeWorkflow.started);
};
... View more
10-07-2020
01:41 PM
|
0
|
0
|
1923
|
POST
|
Thanks that helps alot I'm only dealing with a single type of polygon so don't have any domains/subtypes (and therefore tempates) defined for my layer. Would you happen to know how to get the editor widget to fire an event when the "Add Feature" is clicked?
... View more
10-07-2020
01:04 PM
|
1
|
1
|
2403
|
POST
|
Thanks for the reply! I'm following you now. Just so I'm clear, (I think we may be using different terminology), you're not actually using the Editor Widget (Editor | ArcGIS API for JavaScript 4.16 ) to add features, but rather using a custom feature form to instead?
... View more
10-07-2020
11:04 AM
|
0
|
0
|
3525
|
POST
|
Ed Dempsey Would you have an example of this with the edit widget? I can see how to set a default value in the example you linked to but I'm not sure how to do it using the Edit Widget. Maybe my only option is to make my own Feature Form and use FeatureLayer.applyEdits() ?
... View more
10-07-2020
07:11 AM
|
0
|
0
|
3525
|
BLOG
|
Can this be bypassed by using "inspect element" and just deleting the splash screen element?
... View more
10-07-2020
04:28 AM
|
0
|
0
|
958
|
POST
|
I have a public web app which anonymous users can add new polygon features to. I would like that users cannot see features added by other users. Users will typically add multiple polygons. Enabling "Editors can't see any features, even those they add" is not ideal because the feature instantly disappears when the user adds a new feature. I'd like the polygons added by the user to remain visible until they are finished. Enabling the "Editors can only see their own features " option results in all features submitted by anonymous users being visible to everyone. Is there a way to get the behavior that I want? I was thinking that if I could manually specify the "Creator" field with a random number and enabled "Editors can only see their own features " that this might work but unsure if/how I can do this. Anyone got any ideas?
... View more
10-07-2020
04:07 AM
|
0
|
0
|
195
|
IDEA
|
Andrew Murdoch Did you ever resolve this? I'm suddenly having the same issue for no apparent reason.
... View more
09-28-2020
09:29 AM
|
0
|
0
|
1165
|
POST
|
Micah Cox Did you ever figure this out? I've suddenly lost the ability to filter by extent on infographics. One second everything was fine, the next none of my charts have data and filter by extent is greyed out and checked. I'm at a total loss! Not all, but nearly every web map I have is not doing the same thing.
... View more
09-28-2020
09:25 AM
|
0
|
0
|
606
|
POST
|
I have a large hosted feature service containing lots of parcels, each parcel having different owners. I want to create a webapp for a subset of this data related to a group of of owners in a particular region. To do this I add my features service to my webmap and apply a filter on the layer so that only the parcels belonging to the owners I'm interested in are visible. I've got several other layers in my map also, each with a corresponding owner field. I then use this map in my webapp where I've created a group filter. The group filter is based on the "owner" field in the main polygon layer and the user selects the owner from a drop-down list in the filter. The problem is that the drop-down displays all owners in the feature service (i.e. even though I've filtered the layer on my web map to only include some owners, the group filter ignores this and shows all the owners in the feature service). This means there are owners names visible that don't have any features on the map which is confusing for users. Is there a way to ensure the group filter dropdown only lists values for features that are in my map?
... View more
09-28-2020
07:59 AM
|
1
|
0
|
251
|
Title | Kudos | Posted |
---|---|---|
2 | 10-07-2020 03:45 PM | |
1 | 10-07-2020 01:04 PM | |
1 | 09-28-2020 07:59 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|