Latest Contributions by UndralBatsukh

Hi there,  You cannot change the update graphic for SketchViewModel at this time. It is on our to do list. However, I do not have a timeline for this.  -Undral ... View more

Hi there,  You cannot change the update graphic for SketchViewModel at this time. It is on our to do list. However, I do not have a timeline for this.  -Undral ... View more

Hi there,  So there is a timing issue with sketch update event. We will work on this for 4.13. In meantime, you can wrap the sketch.cancel in setTimeout function. You will see the graphic being selected before it is unselected. setTimeout(function() {   sketch.cancel(); },100); If the approach above does not work then you can set SketchViewModel's updateOnGraphicClick property false, then add your own hittest logic for updating graphics. This sample shows how to use custom hittest logic for updating graphics. ... View more

Hi there,  The issue is fixed at version 4.12. I apologize that this fix was not listed in the release notes. ... View more

Hi there,  I'd suggest adding attributes to your graphics to determine which graphics can be updated or which ones are not allowed to be updated. Then in the sketch's update event, check the selected graphic's attributes to see if the update is allowed. If not then call cancel. This test app should show the general concept. Hope this helps, -Undral   ... View more

Hi there, Thank you so much for reporting this issue. I was able to reproduce the issue. TimeSlider's fullTimeExtent is not being set properly at runtime once it is set first time. We will get this issue fixed hopefully at our next release.  Thanks, -Undral ... View more

Hi there,  I am not able to reproduce the issue. Can you please create a simple reproducible case? You can use this test app modify the code as needed. Thank you, -Undral ... View more

Hi there,  Services with spatial reference in UTM zones (25833) can be used as basemaps. I am assuming your workflow is like the following. I have tested the following workflow with a cached map service with wkid of 25833 and confirmed that it works in 4.10. var layer = new TileLayer({   url:  "yourrurl" }); var basemap = new Basemap({   baseLayers: [layer] }); var map = new Map({   basemap: basemap }); Could you please provide a simple test case if you cannot get it work?  Thanks,  -Undral ... View more

Hi there,  Your observations about the objectIds are correct. It is just how it works as of today. I have created an enhancement request not to override objectIds of graphics added to in memory FeatureLayer. I do not know when it will be implemented in the API. In meantime, you have to query features from your in memory FeatureLayer once applyEdits is completed as shown below. I sense that you already know how to do that. Another suggestion would be to create a new attribute field to keep to track of these unique identifiers? Hope this helps. layer .applyEdits({ addFeatures: addFeatureGraphics }) .then(result => { console.log(result); layer.queryFeatures({ objectIds: [result.addFeatureResults[0].objectId] }).then(function(results){ console.log("features", results.features); }); }); ... View more

Hi there,  I am not sure if I completely understand your workflow. I apologize if I misunderstood your problem and if the following explanation does not address your concern then can you please provide me with a working sample?  FeatureService objectIDs are system generated and we do not have control over it. If you are calling FeatureLayer.applyEdits, featurelayer features (geomery and attributes) are automatically updated for the layer. If you are copying features from a FeatureLayer then adding them to GraphicsLayer lets say and calling applyEdits for the FeatureLayer... then the behavior you are seeing is correct as we do not update client-side graphics attributes once FeatureLayer.applyEdits takes place (they are no longer connected). If you are creating a new feature then updating its attributes and expecting to see the changes in graphics in graphicslayer lets say... I'd suggest that you wait to add the new graphics to graphicsLayer until the applyEdits results are back. Once the applyEdits results are returned, you need to get new objectids, query for the features with those ids, then add the features to your graphicslayer. Do something like the following: // ObjectID is returned in the FeatureLayer.applyEdits. function addNewFeatureToGraphicsLayer (objectId) {   // query feature from the server   featureLayer.queryFeatures({      objectIds: [objectId],      outFields: ["*"],      returnGeometry: true   })   .then(function(results) {     if (results.features.length > 0) {       var graphic = results.features[0];       // if you are creating a new graphic why not wait until the edit results are back?      graphicsLayer.add(graphic);    }  }); } If the new graphics were added to the graphicslayer before applyEdits results are returned, then remove the current client side graphic version and replace the graphic with the new one.  -Undral ... View more

Hi there,  This issue will be fixed at JS API version 4.12 which will be released beginning of July. ... View more