Latest Contributions by Brian_McLeer

The XY to line tool may work for this, but you may need to add x and y fields to both datasets and the common LOCID field would be the common join. Is the relationship 1:1? When you did the XY to line, did you add and calculate the x and y fields or are the in the data already?   https://www.youtube.com/watch?v=p7Qxy1TWWfc ... View more

@MelanieWawryk, I cannot upload an attachment here but this post may help you.  https://community.esri.com/t5/arcgis-pro-questions/toggle-shape-field-visibility/m-p/1563088#M90633 ... View more

Then it looks like after you download and extract the ZIP, remove the spaces from the folder before deploying to inetpub. Thanks @JeffreyThompson2  ... View more

I received a few messages about an error. I remembered that I had to run npm install esri-loader on the client folder before npm ci, npm fund, and npm start. After that on the server folder, I ran npm ci, npm fund, and npm start as well.    ... View more

Thanks @TimWestern, there are a lot of queries going on in the dashboards. I think it seems more of a backend issue than something within the Dashboard, HUB Site, or Experience. I will continue to dig deeper but your insight has provided a new direction to troubleshoot.   ... View more

This morning, I tried a different approach by adding the 6 dashboards to a new Hub site. The dashboard will open in a new tab from the Hub site, but the same results. It seems to be the consensus here that a browser memory issue causes the crash.  ... View more

@JohnWatson_EBA, someone messaged me last week asking for it so I uploaded the ZIP I provided to them. Please let me know if you have any questions or can suggest improvements. Again, credit goes to @FredericPoliart_EsriAU and @DavidDas__GISP.   Update on 11/19/24: Fixed an issue where closing the widget on the toolbar and reopening it caused the widget to remain active at the previous location with buttons not greyed out, even though no point was present on the map. This issue also prevented users from adding a new point, as the widget continued to launch from the prior location state instead of resetting. The ZIP widget below has been updated with the bug fix.  Update on 12/4/24: Esri released Developer Edition 1.16 today. I tested the widget on this version and it looks to function as it did in 1.15. I ran through the same npm commands as above for 1.16.  Update on 3/24/25: I have added the function to disable pop-ups and feature highlights for when the widget is in use. Update on 3/27/25: Updated how buttons appear before user clicks on map. The buttons are always present, but greyed out until user clicks on the map.    Update on 3/28/25: Add accessibility updates to add tooltips when hovering over buttons.  Update on 5/21/25: Add links to Bing Satellite Maps and Bing Streetside. Update on 5/23/25 Added updates to the configurations in DEV so that buttons can be toggled on/off (for example showing Google Maps 3D but turning off Google Street view). The other update is that the URL for Pictometry can now be configured in the DEV settings. With both of these updates, there is no need to go into the code to customize to your parameters and can all be done in Developer Edition.  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. 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

Thanks, @JeffreyThompson2, I will look into these options as well.  ... View more

Thanks, @JeffreyThompson2,  I think the undesirable workaround might be just to have users go to each dashboard individually and not try to have them all in one Experience.  ... View more

@ShengdiZhang I think I resolved the issue, I used your workflow above but turned Overlay off on the Sidebar widget. Thanks for your help with this!  ... View more

@ShengdiZhang I just loaded the foldable template, and out of the box, it is showing the same behavior of not collapsing the map to show the credits when the table is expanded. I added a scale bar as well.  Collapsed:   Expanded:   ... View more