Latest Contributions by Noah-Sager

Whoops! Totally missed that. My apologies. The service requires me to login, but it seems to work at 4.9 with trustedServers  sample: A Pen by noah  ... View more

I think this is related to the responseType of the esriRequest: When this value is  image  the  headers  and  timeout  options are ignored.   esriRequest - RequestOptions - responseType  request | API Reference | ArcGIS API for JavaScript 4.9    If this is the case, we will consider making an enhancement at a future release. ... View more

Hi Todd, you might need to add the domain to the list of trustedServers using esriConfig. example: require(["esri/config"], function(esriConfig) { esriConfig.request.trustedServers.push("[<protocol>//]<hostname>.<domain>[:<port>]"); }); config | API Reference | ArcGIS API for JavaScript 4.9  This changed was described in a recent blog post: https://community.esri.com/community/developers/web-developers/arcgis-api-for-javascript/blog/2018/08/30/cors-and-the-arcgis-api-for-javascript-changes-coming-in-49  ... View more

Hmm. It could be related to the responseType of the esriRequest: When this value is  image  the  headers  and  timeout  options are ignored. esriRequest - RequestOptions - responseType  request | API Reference | ArcGIS API for JavaScript 4.9  If this is the case, we could consider making an enhancement at a future release. ... View more

I think the reason that it works at 4.9 is that WebGL now supports all versions of Server and Online, so labeling will now work with your layers. WebGL is now the default drawing mechanism for FeatureLayer, CSVLayer, and StreamLayer in MapView after having been in beta for a few releases. This includes support for all versions of ArcGIS Enterprise and ArcGIS Online as well as feature collections. Release notes for 4.9 | ArcGIS API for JavaScript 4.9  ... View more

This question might best be posed in the ArcGIS Pro space. https://community.esri.com/community/gis/applications/arcgis-pro  ... View more

Justin is correct. The way to intercept and modify requests is with the RequestInterceptor, introduced at version 4.8.  Release notes for 4.8 | ArcGIS API for JavaScript 4.9  config | API Reference | ArcGIS API for JavaScript 4.9 @Justin, do you have a sample or a code snippet you could share, so we could take a look?  ... View more

It looks like this has been fixed at 3.26: What's new in Version 3.26 | Guide | ArcGIS API for JavaScript 3.26  BUG-000116101: Fixed an issue when using a touch device and panning in Google Chrome browser using Android 9 OS did not work. ... View more

You might want to ask this question in the Python community: Python  This space is more geared towards questions about the ArcGIS API for JavaScript. Thanks, Noah ... View more

In addition to the Web Optimizer, I would also recommend npm and webpack if you are working with the 4.x version of the API, and bower if you are working with the 3.x version of the API. Using npm for Custom Builds | ArcGIS API for JavaScript 4.8  Using webpack for Custom Builds | ArcGIS API for JavaScript 4.8  Using Bower for Custom Builds of the ArcGIS API for JavaScript | Guide | ArcGIS API for JavaScript 3.25  Hope this helps. -Noah ... View more

Correct, at the next release (4.9), we anticipate removing the ability to pass a function to the `field` property of renderers. UniqueValueRenderer | API Reference | ArcGIS API for JavaScript 4.8  Using the valueExpression property as an alternative to using the `field` property should be valid for featureLayer and mapImageLayer, but please note the Known Limitation for sublayers (linked to below). Sublayer | API Reference | ArcGIS API for JavaScript 4.8  ... View more

Hi Saroj, Did Robert's suggestion help you, or are you still having an issue with popups? -Noah ... View more

Sorry for the late reply. Are you still having an issue with the createFeatureLayer() method? Do you have a code sample you could share?  -Noah ... View more

I also confirm the same behavior. Thank you for sharing this information. Apologize for the inconvenience.  To give you a heads-up: at the next release (4.9), we anticipate removing the ability to pass a function to the `field` property, and only allow a string, so this issue would become the expected behavior. One potential workaround would be to use the valueExpression property as an alternative to using the `field` property. Another potential workaround , if you are using version 4.7 or 4.8 of the API, would be to use the createFeatureLayer() method to create a feature layer from the sublayer, then you can use a function for the `field` property. I have tested this and it works properly. Hope this helps, Noah ... View more

Unfortunately, I don't have a solution to share at this time. We are investigating the issue to be addressed at a later release. One option would be to not show those features in the Legend. -Noah ... View more