Latest Contributions by HeatherGonzago

The doc is correct it is currently only implemented for FeatureLayer types. I have added this to our list of enhancements for the Editor. Thanks for the feedback. ... View more

Ok, thanks Todd. Yes, this issue has been addressed. We plan on releasing a patch this week. I'm not sure of the exact date yet. Once it is finished, we'll make sure to note this thread as well. ... View more

We intend to patch this. The problem is not with the FeatureForm, but rather the data that it is using.  The issue is that the featureLayer.applyEdits throws an error when service does not support f=pbf. Could you confirm if this is the case with the data you are using Todd? ... View more

Hi Christophe, Thanks for your help and suggestion. We will take a look at this and see if there is any way we could make this easier to implement for our developers. Thanks, -Heather ... View more

Hi Christophe, The performance work that was done removed some unnecessary geometry queries on the popup. Unfortunately, what worked in the past now needs to be slightly updated to get the geometries like before. In the prior samples, the geometry was included in either the layer or the popup's template. In your specific case, the layer isn't queried for geometries in order to draw features and the popup does not need to query for geometries because it does not need the geometry for anything within the popup, i.e. Arcade expressions. We won't query for the geometries unless they are needed such as in your application. Here is a snippet showing how to do this in your example, https://codepen.io/hgonzago/pen/bGepYKW?editors=1000  view.when(function () {   webmap.when(function(response){     returnedLayer = response.layers.find(function(layer){      return layer.id === "SITG_OPENDATA_01_2709";     });     if (returnedLayer.popupTemplate.outFields == null ) {       // set the outFields on the template       returnedLayer.popupTemplate.outFields = ["*"];     }     //Now you have to wait for the viewModel to be active     view.watch("popup.viewModel.active", function(){       console.log(view.popup.selectedFeature.geometry.type);     });   }); });   I am definitely going to include this in our documentation to help avoid this confusion for any others later down the line. Thank you for questions and samples. // ... View more

Ok, this isn't a bug. The problem is because you need to make sure you specify the PopupTemplate's outfields as well. I updated the non-working sample to include this and the geometry returns correctly now, see https://codepen.io/hgonzago/pen/ExyKZqB?editors=1000 . There were some updates made at 4.17 to help with performance issues so this is probably why you see this problem. Prior to this though, we always recommend setting the outFields in the PopupTemplate. Going forward, if you wish to access the returned geometry like this, you must make sure that this is included. We do discuss this in documentation, but I think we can probably make this easier to find and understand. I will make sure to include some additional information in our next doc update. I hope this helps, Heather ... View more

Thank you Christophe, this should definitely not be happening. Let me look at this and see what may be going on. I appreciate your quick response with info. -heather ... View more

I played around with some of our samples and cannot see this issue, for example, Popup actions | ArcGIS API for JavaScript 4.17  is able to successfully access the selected feature's geometry and performs a measurement without an issues. We'll definitely need to see your app to figure out the issue at hand. ... View more

Hi, we did do some work with help with querying and performance issues but this should not pertain to this issue at all.  The geometry should be there already unless it's not querying for geometries on the layer. Could you please provide a test app showing the issue you are experiencing? Thanks. ... View more

Hi, I'm currently taking a look at this now and will let you know what we find ASAP. Ok, so after some digging, this is definitely a regression (bug) that was introduced at 4.17. We are currently looking into the most feasible way to handle this problem. For now, my best suggestion is to stay at 4.16 for the time-being. We apologize for this and hope to get this addressed very soon. Thanks. ... View more

Stacy, Could you clarify further what you are experiencing? Maybe a test app showing the problem. I have one set up on my end, with date and number fields configured on the server to not allow NULL values. If I remove a value and proceed to the next field input, I always get a warning within the FeatureForm indicating that it needs a valid input. ... View more