Latest Contributions by QunSun

Hi @Goldendelicious , If you are using a custom widget, I think you could give the following approach a try: 1. First, create a client-side FeatureLayer containing only two fields: cityzip and count. You can populate these cityzip values by running a distinct query against the original service, where count represents the filtered quantity for each cityzip, and the geometry comes from the corresponding cityzip polygon in the original service. Then, add this FeatureLayer to the map for statistical display purposes—let's temporarily call it the statistics display layer. 2. Create a renderer for the statistics display layer based on the count field. You can use either a UniqueValueRenderer or a ClassBreaksRenderer. 3. When filtering by different attributes, send a statistics request to the feature service to aggregate count by cityzip, passing your attribute filters in the where clause. This will return a result structured like { cityzip: count }. Then, use these statistical results to update the count values in the statistics display layer. Since the renderer was already applied to the layer in Step 2, updating the count field will automatically refresh the layer's symbols. ... View more

Hi @MattCashen , thank you for reporting this issue. You mentioned two cases (scale 282 and scale 283). Let me explain them separately. This is the basemap used by the app - https://services.arcgisonline.com/arcgis/rest/services/Elevation/World_Hillshade/MapServer.   I was happy to see the implementation of scale limits for maps within experience builder.  However, I'm running into some unusual behavior with mine.  My map has many cache layers in it and right now they are all cached down to the 282 scale.  I've been playing around with setting the map scale limit at 282.  I have the search widget in my experience and one of the layers you are able to search is parcels.  I have the search tool set up with the action to select and zoom to a parcel after a successful search is done.  The zoom is set to automatic zoom scale.  Currently if you search for a smaller parcel it zooms down to the 282 scale, but my cache layers disappear as if it the current scale level is outside the cached scales.   It is an bug for scale 282. The final scale range is affected by the map LODs. The initial max scale is 282 (view.constraints.maxScale). The API will look for a scale in LODs that is greater than 282 and closest to 282. This scale is 282.124294, so 282.124294 is the final scale (view.constraints.effectiveMaxScale) used by the API. When searches for parcels, the zoom-to message action calls view.goTo(extent) to change the extent of the map. However, after calling this method, the value of view.scale is 282.1242939999793, which is close to view.constraints.effectiveMaxScale (282.124294), but it is still smaller than effectiveMaxScale, which is wrong. effectiveMaxScale should be effective for all scenes to ensure that view.scale >= view.constraints.effectiveMaxScale, so this should be an API bug.  We will fix this issue in the next release.   Even more peculiar is that if I set the map scale limits to 283 and repeat the process it then zooms down only to the 564 scale.  And after this is done you are not even able to manually zoom the map in beyond 564 using either the scroll wheel or the map zoom buttons.   It is the expected behavior for scale 283. As mentioned above, the final scale range will be affected by the map LODs. The initial max scale is 283 (view.constraints.maxScale). The API will look for a scale in LODs that is greater than 283 and closest to 283. This scale is 564.248588, so 564.248588 is the final scale (view.constraints.effectiveMaxScale) used by the API. So this is the expected behavior. I think you can set the scale to 283 as a workaround now, we will fix the issue in case1 in the next release.   ... View more

@MohammedHilal_K Can you try calling jimuMapView.addLayerToMap() serially to solve this problem? Similar to the following code async function addMultipleLayersToMapOneByOne(items) { for (const item of items) { const { dataSourceId, targetLayerId } = item; await jimuMapView.addLayerToMap(dataSourceId, targetLayerId); } } ... View more

@MohammedHilal_K    Thanks for providing more details. This is a bug and will be fixed in next release. ... View more

Hi @MohammedHilal_K ,   Are there any errors in the browser console? Which data actions are missing? Is it only zoom to and pan to that are missing, or are they all missing? It would be great if you could upload a screenshot of the data actions. ... View more

Hi @PartyPelican , For performance reason, JimuLayerView will not automatically create data source. If data source has been created by some widgets, then JimuLayerView.getLayerDataSource() gets the data source. If the data source has not been created, you can create the data source through the asynchronous method JimuLayerView.createLayerDataSource().   ... View more

This is a breakchange of JS API. From JS API 4.27, The Popup widget loading is deferred until the view is ready and finished updating, and will only be loaded if View.popupEnabled is set to true (which is the default), when View.openPopup() is called, or when some widgets need the popup, such as Search.  That is to say, in API 4.26, after View is initialized, View.popup is a Popup instance, but in API 4.27, after View is initialized, View.popup is just an ordinary object. Only after calling the View.openPopup() method, View.popup will become a Popup instance. See details here - https://developers.arcgis.com/javascript/latest/breaking-changes/#427   I think you can call View.openPopup(), when this method is resolved, you can call view.popup.fetchFeatures(). ... View more

ArcGIS JavaScript API doesn't support border for highlight options, see details here - https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View.html#HighlightOptions ... View more

Hi ShahranNewaz, Is your problem that you don't know the id of the layer to be exported? If you don’t know the layer id, how do you know which layer to export? ... View more

Hi MohammedHilal_K, The webmapId is not the correct dataSourceId. Data source is a concept in Experience Builder. The only way to select a webmap/webscene data source is using the left data panel. Then you can check the dataSourceId by _appState.appConfig.dataSources in the console. Here is an example. The dataSourceId of the webmap is "dataSource_1", not the webmapId "33e58168249b42d49c4fb1b4f27728db". ... View more

Hi MohammedHilal_K, Currently only Map widget can create JimuMapView. Can you share your code to create JimuMapView in the custom widget ?   ... View more