Latest Contributions by TylerKirk

Thanks for the response. I already understand how to utilize applyEdits for client-side FeatureLayer manipulation. My question was about the client-side FeatureLayer graphic's visible property not working and if the API will support it like it once did in the 4.9. ... View more

Checking the latest version (4.15) the visible property on a Graphic is ignored for client-side FeatureLayers; will this ever be addressed or will the documentation be updated to specify it doesn't work for client-side FeatureLayers? Are there any FeatureLayer specific workarounds? ... View more

I was already planning on moving forward with your second suggestion, "create a new attribute field to keep to track of these unique identifiers". Let me know when this is addressed though so I can remove the workarounds at that time. Thanks Undral! ... View more

Thanks Undral for the response! Let me better explain my workflow. Upon startup 1. Query json REST endpoint 2. Convert json data to list of graphics. There is an existing identifier in the data that is set to the object id field in the graphic. 3. Create client side FeatureLayer from graphics. Successive polls 1. Query json REST endpoint 2. Convert json data to list of graphics. There is an existing identifier in the data that is set to the object id field in the graphic. 2. After querying the feautreLayerView, determine which graphics need to be updated, deleted, and added by comparing object id fields between the latest graphics from the rest endpoint and the graphics from the featureLayerView query 3. Use the featureLayer.applyEdits method to update the featurelayer graphics The issue that I am seeing is that when graphics are added to a client side featurelayer through the applyEdits method, the object ids for the graphics are changed from what was passed in to whatever the featurelayer decides their objectids should be; which appears to be "calculated by incrementing the max existing object Id".   When graphics are first added to the featurelayer through the source field, their object ids do not change. Ended up creating codepen to showcase the behavior I'm seeing. https://codepen.io/MotoTK/pen/voRLpY?editors=0010  ... View more

In the 4.12 version of the API I am still seeing the behavior noted above: "Two features with objectIds set in the attributes are passed to applyEdits(), but when being added the object Ids are automatically calculated by incrementing the max existing object Id and the attribute value is disregarded." As Nick Cameron originally asked, is this expected behavior/by design? I need attribute objectId values passed in to the applyEdits addFeatures array to match the objectId values from the generated graphics after the applyEdits finishes as my data source sends out updates to existing features; if the objectId value is changed by the addFeature applyEdits then how am I supposed to use the applyEdits updateFeatures capability if the graphics rendered on the client don't match the objectIds sent from the data source? ... View more

I am also having issues with the graphic's visible property, in my case 2D. If a graphic is added to a GraphicsLayer with a visible value = false, the graphic is still displayed. There seems to be timing issue with setting the Graphics visible property as if it is done after a certain time, the graphic's visibility will match that of the visible property. In this JS Bin example, the polygon's visible property is set to false but is still visible in 2D. The point graphic's visible property is toggled every second and this works in both 2D and 3D. ... View more