Latest Contributions by Noah-Sager

Hi @PaoloF, this shouldn't be an issue with Angular, but the issue might have to do with how you are using apiKeys. Can you share a simple reproducible test-app with JavaScript that shows how you are trying to use an apiKey? Also, are the resources hosted in ArcGIS Online?  https://developers.arcgis.com/javascript/latest/release-notes/#api-keys   ... View more

Hi @ManasMahajan, currently, there is no easy way to do this. We have some enhancements coming for routing that this will make this simple to do in the near future. ... View more

I think the issue is that the custom print service was published from ArcMap. Can you try republishing with ArcGIS Pro? We have a some known limitations with publishing print services from ArcMap. ... View more

Hi @ADITYAKUMAR1, thanks for the question. So it sounds like the map prints correctly with the Esri utility print service, but you are seeing issues with your custom print service? Was your print service published from ArcMap, or ArcGIS Pro? You want to use a print service published from ArcGIS Pro. For print service publishing/sharing troubleshooting, I would recommend this doc: https://enterprise.arcgis.com/en/server/latest/publish-services/windows/tutorial-publish-additional-layouts-for-printing-with-arcgis-pro.htm Another troubleshooting step you can take is to make sure that the layers are included in the export_webmap request by inspecting the execute request in the browser developer tools network tab. ... View more

Hi @GertConradie, thanks for the question. With the default service, the print widget can include or not include the legend: https://developers.arcgis.com/javascript/latest/sample-code/sandbox/index.html?sample=widgets-print My hunch is that this issue is related to how the custom print service was configured prior to publishing. Here is some information about sharing a custom print service from Pro: https://enterprise.arcgis.com/en/server/latest/publish-services/windows/tutorial-publish-additional-layouts-for-printing-with-arcgis-pro.htm     ... View more

@viewprogisdev - at 3x, we have a setRequestPreCallback method that is fairly similar. See here: https://developers.arcgis.com/javascript/3/jsapi/esri.request-amd.html#esrirequest.setrequestprecallback   ... View more

Ok, this sounds like a snapping scenario. Are you trying to update the vertex coordinates to a specific feature? If so, we are working on this functionality for a future release. It's also worth noting that for very precise measurements, the GeometryEngine would be a good choice. ... View more

Hi @nidaaktan, overall, what are you trying to accomplish? I would not recommend using undocumented or private properties as they are not supported and could change anytime. ... View more

Hi @ColinGowens, the API should work fine with a composite geocoder. Here is an example app: https://codepen.io/noash/pen/qBrRrPa?editors=1000 My hunch is that the issue is related to the composite geocoder itself. I found this thread with some tips about publishing a composite geocoder from Pro that might be useful: https://community.esri.com/t5/arcgis-online-questions/composite-address-locator/m-p/732528 If you want to share the URL to the geocoder you are using (if it's public), I can test with it as well. ... View more

Interesting. To be clear, the latest version it works at is 4.15 or 4.16? I don't see any changes to Search at 4.16 or 4.17, which also makes me wonder if there are issues with other widgets with these frameworks. It also might help if you could zip up an entire simplified project and send it over for further investigation. You can message me directly if you don't want to post it here. ... View more

Hi @ShellyM, I think we're making progress. I worked with the infamous Rene Rubalcava on this and we got a test-app with React and esri-loader that seems to work fine:  https://codesandbox.io/s/agitated-leavitt-1phqw?file=/src/App.js If you're using class based React components, it sounds like there could be some DOM update interactions that are causing the issue. With lots of "this" references and the React DOM stuff, it's difficult to say for certain though.   ... View more

Ok, thanks for the update. Let me do some additional digging and I'll respond back here when I have an update. ... View more

Excellent. This is progress. Can you try instantiating the Search widget the same way in the React app? Instead of initializing it with an empty array for the sources, and then adding the layerSource to the widget. ... View more