|
POST
|
12/10/2025 (for 1.19 version only): Theme Typography Update – All widget text now uses Experience Builder’s Theme Typography for consistent styling. Accessibility Improvements – Added multiple WCAG-compliant updates across widgets for better usability and accessibility.
... View more
2 hours ago
|
0
|
0
|
2
|
|
BLOG
|
12/10/2025 (for 1.19 version only): Theme Typography Update – All widget text now uses Experience Builder’s Theme Typography for consistent styling. Accessibility Improvements – Added multiple WCAG-compliant updates across widgets for better usability and accessibility.
... View more
2 hours ago
|
0
|
0
|
5
|
|
POST
|
Hi @EricLacoursierePQ, I just sent you a direct message with an updated ZIP file. I tested on my end and the issue looks to be resolved. If your testing works out and the issue is resolved, I will update this post.
... View more
yesterday
|
0
|
0
|
10
|
|
POST
|
I was having some issues with my print service, and I changed it from Synchronous to Asynchronous which helped some for the service. Also are you using a dedicated or shared instance for the service? I changed it to dedicated with 6 max.
... View more
yesterday
|
0
|
1
|
48
|
|
BLOG
|
Thank you for all of the snippets @GeoguichetGeoguichet, I will review these and see if I can replicate behavior and see if we can get an update on our end in the near future.
... View more
|
1
|
0
|
26
|
|
BLOG
|
@PiotrCienin thank you for the idea, this update has been completed. Please see notes below. Added a function to allow for any coordinate system for the Copy Coordinates function, not just Web Mercator in the settings panel. New function added in 1.19, did not test in 1.18. Article original 1.18 version without new function and 1.19 function with new function. May be backwards compatible in 1.18 but I did not test.
... View more
a week ago
|
1
|
0
|
185
|
|
BLOG
|
Hello @PiotrCienin , thank you! I could look at adding this as a configuration in the settings panel.
... View more
a week ago
|
1
|
0
|
198
|
|
POST
|
Is there an ETA for resolving this BUG? It was reported at 1.16 and is still present at 1.19 in DE. https://support.esri.com/en-en/bug/the-order-of-attribute-fields-changes-in-the-output-whe-bug-000174735
... View more
4 weeks ago
|
1
|
1
|
209
|
|
BLOG
|
Overview The Map Switcher widget provides a dropdown interface for navigating between different Experience Builder applications while preserving the current map extent and zoom level. The widget captures the URL hash fragment from the source application and appends it to the destination URL. Note: An earlier version of this widget had hardcoded URLs in the code, which prevented it from being shared on the Esri Community. Experience Builder 1.19 introduced breaking changes that required the widget to be redeveloped. This version allows administrators to configure URLs through the widget settings panel, making it suitable for broader distribution. Configuration Settings The widget settings panel contains the sites configuration: Sites Configuration: Label: The display name that appears in the dropdown URL: The full URL to the target Experience Builder application Multiple sites can be added using the "Add Site" button. Sites can be removed using the "Remove" button for each entry. The widget does not require a map widget connection. Widget Functionality The widget displays a dropdown menu with the configured site options. The placeholder text reads "Select map to view". Functionality: When a user selects a destination from the dropdown: The widget captures the current URL hash fragment (everything after the # symbol) This hash contains map state parameters: center coordinates, zoom level, scale, rotation, and spatial reference The widget appends this hash to the selected destination URL The browser navigates to the new application Features: Works with any coordinate system (Web Mercator, State Plane, WGS84, etc.) Preserves center point, zoom level, and rotation URLs configured in settings panel
... View more
4 weeks ago
|
2
|
0
|
264
|
|
POST
|
Developer Edition 1.19 was released today (11/13). I tested the widget and everything looks to functioning the same as it was at DE 1.18.
... View more
4 weeks ago
|
2
|
0
|
137
|
|
BLOG
|
Developer Edition 1.19 was released today (11/13). I tested the widget and everything looks to functioning the same as it was at DE 1.18.
... View more
4 weeks ago
|
0
|
0
|
106
|
|
BLOG
|
Developer Edition 1.19 was released today (11/13). I tested the widget and everything looks to functioning the same as it was at DE 1.18.
... View more
4 weeks ago
|
0
|
0
|
448
|
|
POST
|
Update on 11/13/25: Breaking changes going from DE 1.18 to 1.19: Experience Builder 1.19 introduces two critical breaking changes that prevent widgets built for 1.18 from loading. First, the WidgetState enum has been removed from 'jimu-core', requiring developers to replace WidgetState.Opened with the string literal "OPENED" in widget lifecycle methods. Second, and more significantly, the jsx() function signature has changed to align with React 17+'s new JSX transform—children must now be passed as a children property within the props object rather than as separate function arguments. This means jsx('div', {props}, child1, child2) must be rewritten as jsx('div', {props, children: [child1, child2]}) throughout the entire render method. While this is a substantial refactoring effort requiring updates to every jsx call in your widget, it brings Experience Builder in line with modern React standards and is a one-time migration requirement for the 1.18 to 1.19 upgrade path. Note: This post includes both v1.18 and v1.19 versions of the widget for reference, allowing developers to compare the before and after implementations to better understand the required migration changes.
... View more
4 weeks ago
|
0
|
1
|
76
|
|
DOC
|
11/13/2025: Breaking changes between Developer Edition 1.18 and 1.19: Upgrading ArcGIS Experience Builder Widgets from 1.18 to 1.19: Breaking Changes Experience Builder 1.19 introduces two critical breaking changes that prevent widgets built for 1.18 from loading. First, the WidgetState enum has been removed from 'jimu-core', requiring developers to replace WidgetState.Opened with the string literal "OPENED" in widget lifecycle methods. Second, and more significantly, the jsx() function signature has changed to align with React 17+'s new JSX transform—children must now be passed as a children property within the props object rather than as separate function arguments. This means jsx('div', {props}, child1, child2) must be rewritten as jsx('div', {props, children: [child1, child2]}) throughout the entire render method. Every jsx call in your widget needs updating, with all child elements explicitly specified in the children prop (e.g., jsx('h2', { style: {...}, children: 'Title' })). While this is a substantial refactoring effort, it brings Experience Builder in line with modern React standards and is a one-time migration requirement for the 1.18 to 1.19 upgrade path. I have posted both a 1.18 and a 1.19 version in this update to work on both versions.
... View more
4 weeks ago
|
0
|
0
|
492
|
|
BLOG
|
Thank you for the feedback @GeoguichetGeoguichet . Would you mind sending me a private message with your widget in a ZIP file? Currently we don't have plans for a V3, but we may be able to patch V2 with your bug findings.
... View more
4 weeks ago
|
1
|
0
|
913
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 4 weeks ago | |
| 1 | Monday | |
| 1 | a week ago | |
| 1 | a week ago | |
| 1 | 10-15-2025 12:02 PM |
| Online Status |
Online
|
| Date Last Visited |
2 hours ago
|