Latest Contributions by ReneRubalcava

Ok, I think you need to simplify your sample a bit to get to the bare minimum and work up from there. Looks like I was incorrect about removing graphics from the graphicsLayer used by SketchViewModel. If you no longer want to use them in a Sketch, you can remove them, but if you still want to see them, you need move to another graphicsLayer not used by Sketch. There's some snippets using this pattern for when you use sketch.create(), but you are sketching your own graphics with sketch.update(), so it's slightly different, as you provided the graphic for the SketchViewModel. Here is a super simple sample showing how to sketch a given graphic, and finish the sketch. https://codepen.io/odoe/pen/abYWVaK?editors=0010 I think in your previous example, you are trying to delete things before completing the Sketch action and that's causing issues.   // on click, stop the sketch actions sketchBtn.addEventListener("click", () => { // if the sketch is currently active // we can complete the action if (sketchViewModel.state === "active") { sketchViewModel.complete(); } }); sketchViewModel.on("update", (event) => { // this fires after sketchViewModel.complete() if (event.state === "complete") { // you do need to remove graphics from // the grapicsLayer so they are not part // sketch updates graphicsLayer.removeMany(event.graphics); // move it to another graphics layer // so I can still see it, but not sketch it // anymore view.graphics.addMany(event.graphics); } }); const clickHandle = view.on("click", ({ mapPoint }) => { clickHandle.remove(); const graphic = new Graphic({ geometry: mapPoint }); graphicsLayer.add(graphic); sketchViewModel.update(graphic, { tool: "move" }); });   ... View more

Technically, this is what the Editor widget is for. But if you really wanted to, you could pass the graphics from the Sketch widget into the featureLayer.applyEdits, but kind of seems like the long way to get there. Plus you would need to populate the attributes in some way. You would need a separate FeatureLayer per geometry type as well. ... View more

Custom Search sources are going to vary based on what third-party API you are using. So you need to be familiar with the parameters that API needs. The samples are using the esriRequest to make the queries, but you don't have to. You can use native fetch, or axios, or any other request style library you are comfortable with. https://developers.arcgis.com/javascript/latest/api-reference/esri-request.html The ?q= is created by esriRequest, because that is how the sample API needs to be parsed. Your API is different. The %2F comes from url encoding. Without going into detail, this is how URL requests get encoded to escape special characters. This is standard. This was specific to the sample API being used, your API will require different parameters. Your API doesn't need the lat/lon parameters, so you can omit them. The sourceIndex is the index of the search source being referenced. This is given to you in the parameters of the getSuggestions method. https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Search-SearchSource.html#GetSuggestionsParameters The power of using custom search sources is that you can transform any searchable third-party API into something that be used by the Search widget, meaning each API will need to handled on a case by case basis. The API parameters will differ, the results will differ, but as long as you transform those results into something the ArcGIS JSAPI expects, you can make it work. This Swiss search API can return GeoJSON results, so that makes it a little easier to work with, but you need to specify the spatial reference as well. Here is an update to your app that uses the parameters as described in that search API doc and seems to work correctly. https://codepen.io/odoe/pen/QWmpVdQ?editors=0011 ... View more