Latest Contributions by LefterisKoumis

ArcGIS Enterprise 12.1 is already released. It is available for download. However, as I stated in my post we are in the dark about the compartibility with React, Calcite, developer version and ExB version.

Esri recently released ArcGIS Enterprise 12.1, but we are still waiting for a compatible version of ArcGIS Experience Builder (ExB). According to the ExB release compatibility matrix, the most recent Experience Builder Developer Edition version supported by ArcGIS Enterprise 12.0 is based on ExB 1.18, while newer Developer Edition releases are available. I attempted to develop a custom widget using React 19 and Experience Builder Developer Edition 1.19, then deploy it to an ArcGIS Enterprise 12.0 portal. However, I encountered compatibility issues during deployment. Based on Esri's blog announcement, Experience Builder 1.21 was expected to be released in May 2026. Until a compatible version becomes available for ArcGIS Enterprise 12.1, we are unable to take advantage of React 19 and other enhancements provided by the newer Experience Builder releases when developing custom widgets for deployment to Portal for ArcGIS 12.1.

Will this table be upgraded? Is version 12.1 compartible with developer version 1.20, react 19? Last time I checked the latest versions to work with ArcGIS Enterprise 12.0 were with ExB 1.18, react 18 and developer version 1.18. https://developers.arcgis.com/experience-builder/guide/release-versions/

Version 12.0 fixed these issues?

‎05-11-2026

Question to the ESRI team. Can you use AI on a map loaded with feature layers? I usually don't use webmaps. The users of the app can add layers from a list of available feature layers where they can perform their spatial/attribute queries. Can the AI be used? Thank you.

‎02-12-2026

This page is titled "Use Map Components (React 19 + Web Components)" and it provides instructions to download the SDK to a new folder on your ExB development environment called "web-component-widgets/use-web-components-19". React JS 19 uses functional components. Under the "Contents" version it states: The issue I see is that at the SDK location it still uses class components. For example, the "add-layers" sample it states that it was updated to version 1.19 but the script suggests otherwise. render () { const style = css` form > div { display: flex; justify-content: space-between; input { width: 100%; } button { min-width: 100px; } } ` return ( <div className="widget-addLayers jimu-widget p-2" css={style}> {this.props.hasOwnProperty('useMapWidgetIds') && this.props.useMapWidgetIds && this.props.useMapWidgetIds.length === 1 && ( <JimuMapViewComponent useMapWidgetId={this.props.useMapWidgetIds?.[0]} onActiveViewChange={(jmv: JimuMapView) => { this.setState({ jimuMapView: jmv }) }} /> )} <p>{defaultMessages.instructions}</p>

‎02-06-2026

You are correct. I was making a novice error on the directions of the starter widget.

‎02-06-2026

The Experience Builder online documentation needs badly a update on all pages to reflect the changes that come with ArcGIS ExB 1.19, ReactJS 19 and Node JS 22. For example, the ExB starter widget as instructed here, it cannot be implemented as described because you will get a webpack error due to incompatibility with the newer version of Node.js. In the newer versions of React JS., only function based components are used, but sadly most of the ESRI ExB documentation still refer to the class based components. @Jianxia ?

‎01-08-2026

I have an update @Sage_Wall and @LaurenBoyd. I used the suggested script and I realized that sometimes the reactiveUtils.watch is not triggered and sometimes it does. I don't what are reasons behind it. So, I modified to use the arcgisPropertyChange property. so instead of reactiveUtils.watch( () => arcgisFeatures.features, () => { checkIfFeaturesEmpty() }) I use this arcgisFeatures.addEventListener("arcgisPropertyChange", (event) => { if (arcgisFeatures.features.length>0) { checkIfFeaturesEmpty(); }

‎01-08-2026

Thank you so much @Sage_Wall and @LaurenBoyd . It makes sense since the fetchFeatures makes calls to the server and we have to wait until it retrieves the feature info. I think this is a good example to add to the documentation since I noticed that there are not many examples of using mapimagelayers with the web components.

‎01-08-2026

@Sage_Wall Are you suggesting to set the fetchFeatures to false and use the identify to collect the features from an mapimagelayer? If that's the case what is the use of the fetchFeatures? await arcgisFeatures.open({ location: mapPoint, features: [graphics] fetchFeatures: false }) For featurelayers we can use this and we don't need fetchFeatures. arcgisFeatures.open({ location: mapPoint, features: [graphics] });

‎01-07-2026

I use this script to display the popup in the arcgis-features. I need to determine if the arcgis-features after it runs if it is empty or found features. If i click on a featurelayer , then the console states that the component is not empty. However, if i click on a mapimagelayer it states that the component is empty even though there is a feature inside the arcgis-features. Why? const hitTestResult = await arcgisMap.view.hitTest(screenPoint); const mapPoint = arcgisMap.view.toMap(screenPoint); await arcgisFeatures.open({ location: mapPoint, features: results.map(r => r.graphic), // Include any client-side features found fetchFeatures: true }).then((response) => { checkIfFeaturesEmpty() }) function checkIfFeaturesEmpty() { if (arcgisFeatures && arcgisFeatures.features) { if (arcgisFeatures.features.length === 0) { console.log('The <arcgis-features> component is empty.'); return true; } else { console.log('The <arcgis-features> component is not empty and contains ' + arcgisFeatures.features.length + ' features.'); return false; } } else { console.log('The <arcgis-features> element or its features property is not available yet.'); return null; } }

‎01-07-2026

@Sage_Wall If you have a mapimagelayer, then it will still show "No feature hit" in the console. hittest works for featurelayers. How can you modify the script to show hit featureLayer/no feature hit if you are using a feature layer and a mapimagelayer.

‎01-06-2026

Yes, thank you—I’m aware of that. My question, however, is about changing the “No layer” text. Since the application may have multiple layers added dynamically by the user, I’d prefer the message to prompt the user to click the layer stack icon and select a layer in order to populate the table.

‎01-05-2026

When the layer-url property is not set at design time, <arcgis-feature-table> shows the layer list icon with the message “No layer”, even if users add layers later during runtime. Is there a way to replace this message with something like “Click the icon to display tables for available layers”? As it stands, users are not clearly informed that clicking the icon reveals the list of feature tables. @Sage_Wall @ReneRubalcava

Online Status	Offline
Date Last Visited	2 weeks ago

My Ideas

Latest Contributions by LefterisKoumis

Re: ExB compartibility

ExB compartibility

Re: What's Coming in ArcGIS Experience Builder in ArcGIS Enterprise 12.1

Re: Experience Builder in ArcGIS Enterprise 11.5 Constant React JS Error

AI on custom map?

React 19 & ExB

Re: Please Update Experience Builder Documentation.

Please Update Experience Builder Documentation.

Re: arcgis-features and mapimagelayer

Re: arcgis-features and mapimagelayer

Re: arcgis-features and mapimagelayer

arcgis-features and mapimagelayer

Re: Using Components with hitTest: 'click' on Calcite Buttons registers as hitTest in underlying Map

Re: Feature Table web component

Feature Table web component

Re: ExB compartibility

ExB compartibility

disable popup on map using map component

Please Update Experience Builder Documentation.

Re: arcgis-features and mapimagelayer

Experience Builder Custom Widgets

GIS Jobs

Web AppBuilder Custom Widgets