Latest Contributions by UndralBatsukh

Yes it is fixed at 4.15. ... View more

Hi there,  Is it possible for you to share the csv file you are uploading create this service? The issue appears to be related to the service, the tiled request is returning a 400. Getting the csv file will help to troubleshoot the issue. ... View more

Hi there,  At this time, it is an expected behavior. 4.x labeling engine checks if labels are on exact same spots and keeps one for performance reasons. This behavior is on our radar and we will be enhancing the labels engine to count for scenarios like this one.  You could add an another layer with no fill and controlling the labels there. -Undral ... View more

Hi there,  You should listen to events on your graphics collection. You can capture them as shown below: layer.graphics.on(["before-remove", "after-remove"], function(event){ // process your logic here before and after the graphic is removed }); layer.graphics.on("after-remove", function(event){ // process your logic here after the graphic is removed });‍‍‍‍‍‍‍ ... View more

It will be released towards end of next week. You will see announcement here on geonet when it becomes public. In meantime, you can test this functionality using our next version.  Please take a look at this test app to see how globalIds are used with FeatureLayer.applyEdits. It is not the most intuitive app but will get the concept across.  To add a new features, click on the `Add Feature` button, then click on the map, change the severity value and provide a globalId for your new feature and finally click on the `Apply Edits` button.  To update an existing feature, click on a feature on the map, then change the severity value, click on the update feature button and finally click on the Apply Edits button.  I would like to point out that globalIds are supported for update and add operations for applyEdits. For delete operations you must use the objectIds. This will become available at 4.16.  Hope this makes sense, -Undral ... View more

Hi there,  Seems like you are using 3.x API to edit features using globalIds. 3.x FeatureLayer.applyEdits does not support globalIds. This functionality will be supported at 4.15.  -Undral ... View more

As for your second comment, do you mean to filter the layers? As for the layer, you can definitely use the filter and effect.  It won't work for the labeling because the labeling optimization happens before filtering.  Please let me know if you need more info.  Hope this makes sense, -Undral ... View more

Hi there,  You are absolutely on the right track for the workaround. I would do exactly what you suggested. I am thinking maybe adding another layer with no fill and controlling the labels there? ... View more

Hi there,  At this time, it is an expected behavior. 4.x labeling engine checks if labels are on exact same spots and keeps one for performance reasons. This behavior is on our radar and we will be enhancing the labels engine to count for scenarios like this one.  I added your information to our issue system.  -Undral ... View more

Check out this test app to see how it works. Hopefully, it will point you to a right direction. -Undral ... View more

Hi there,  Please take a look at [this test app](https://codepen.io/U_B_U/pen/dyojOLd?editors=1000). I cleaned up the code (which I should done in the first app) and graphic now has pictureMarkerSymbol. GraphicsLayerView.highlight is highlighting the graphic with picture marker symbol.  But I am glad to hear that you are using client-side FeatureLayer. It is better to use client-side layer over GraphicsLayer anyway.  Cheers, -Undral ... View more

Make the following change in your code: featureLayer.queryFeatures({ geometry: view.center, returnGeometry: false, orderByFields: ["WMA_Name"], distance: 500, units: "miles" })‍‍‍‍‍‍‍ ... View more

Yes you should modify the query parameters to meet your needs. So LayerView.queryFeatures() returns features only available for drawing on the client side. If you must query all features in your service then you must use FeatureLayer.queryFeatures() method. This will issue a network request to your service. So you should change your code to use layer.queryFeatures instead of layerView.queryFeatures() method. I want to point out the following query parameters will create a 10 mile buffer around the view extent. So you need to decide on within 500 miles of what? The view.extent? View center? User defined location? You as a developer need to be responsible for setting the geometry for your query. layerView.queryFeatures({   geometry: view.extent, view.center? user defined location?   returnGeometry: true, => Set to this to false if you do not need geometries   orderByFields: ["WMA_Name"],   distance: 10,   units: "miles"  }); Also how many features do you have in your service? Querying features within 500 miles sounds like may put strain.  When you query features do you need to get geometries? If not, then set your returnGeometry to false. Do you only need certain attributes? Then please specify outFields property on your query parameter.  Take a look at this sample to see how spatial queries work.  ... View more

In your first section, all you have to add is distance and units to your query parameter. FeatureLayer.queryFeatures() accepts query parameter. As I pointed above, you can specify distance and units on your query.   layerView.queryFeatures({   geometry: view.extent,   returnGeometry: true,   orderByFields: ["WMA_Name"], distance: 10, units: "miles"  }); Is this what you are referring to? ... View more