topic Re: Experience Builder woes in ArcGIS Experience Builder Questions

Experience Builder woes

JoshWhite — Fri, 07 Jan 2022 17:55:32 GMT

I am really struggling here. I am a Web App Builder hold out because the Experience Builder still lacks the functionality that I need. I need a search widget that gives me more options on what to do. The current search widget gives me a result but doesn't actually do anything, it won't pan to the result. It does add something to the url which when submitted will redirect. That is certainly less than ideal. There is also still no way to print a map which my users still want. I would love to be able to move to EB because I really need the grouping functionality that WAB does not offer, but I cannot make the move without these widgets. Its been several years now since the EB was developed and widgets are always promised. What ends up happening is these advanced widgets end up getting updated like Elevation Profile, Suitability Modeler which are great features if you need them but still not very helpful if the basic widgets are not working. Why are features like WAB that actually work not getting updated instead of developing new features like EB?

Re: Experience Builder woes

jcarlson — Fri, 07 Jan 2022 18:42:49 GMT

To answer that last question, it's because WAB is built on the ArcGIS JS 3.x API, which is in the process of being phased out in favor of tools built on the 4.x API. You can think of EB as not so much an alternative to WAB as the 4.x version of it.

That said, EB is very different in how widgets interact, particularly because EB allows from any number of different maps (including none!) to be added to the same experience. To get things like the Search widget to "talk" to your other widgets like maps and lists, you need to add triggers. For instance, I have a search widget that, upon selecting a record from the search results, will automatically send a "Zoom to" message to my Map widget.

I can easily set additional triggers to apply to other maps, or non-spatial widgets.

I don't have any useful information about the Print widget, except that it's supposed to be on the roadmap for the "near term" 2022. We've just been giving our users a tutorial of how to take screenshots on their computer, and that seems to have alleviated some of the "print the map" requests for the time being.

Re: Experience Builder woes

JoshWhite — Fri, 07 Jan 2022 19:13:48 GMT

Josh,

I appreciate that response. I didn't realize that a trigger had to be set in this case. The terminology used is not very intuitive. Even after finding the help, I still just guessed which trigger was the best and "record selection changes" is what I landed on. I'll keep working on this map and see if I can get it to do what I want. I actually have used EB for some other apps but this particular one just has extra requirements. To be honest, my post was more venting than anything because I feel that Esri is not as responsive to user requests as they used to be.

Re: Experience Builder woes

DanMallett — Sat, 08 Jan 2022 00:01:06 GMT

Worth pointing out that the incredible @RobertScheitlin__GISP has 2 custom ExB widgets including a Print (and more to come):

https://community.esri.com/t5/experience-builder-custom-widgets/tkb-p/eb-custom-widgetstkb-board

Re: Experience Builder woes

JoshWhite — Mon, 10 Jan 2022 14:09:19 GMT

I'm not using Developer Edition though. Is it possible to use custom widgets in the ArcGIS Online version?

Re: Experience Builder woes

RobertScheitlin__GISP — Mon, 10 Jan 2022 14:12:16 GMT

@JoshWhite

Nope custom widgets require developer edition.

Re: Experience Builder woes

JoshWhite — Mon, 10 Jan 2022 14:21:22 GMT

That's what I thought. Going that route really isn't a good option for me at this time. Perhaps Esri should consider bringing you on as a consultant. I know you did great work with Flexviewer and with WAB and I'm sure this one is just as good.

On another note, I am thinking of going ahead and deploying my EB map and just not discontinuing the WAB until I am absolutely satisfied with the new widgets. Once that happens I can phase out my support of our WAB apps.

Re: Experience Builder woes

RobertScheitlin__GISP — Mon, 10 Jan 2022 14:33:46 GMT

@JoshWhite

WAB still have a couple of years. I am still using WAB as my main site I have a EB site that I am testing but am still not happy with it yet. No need to be in a hurry.

Re: Experience Builder woes

ahargreaves_FW — Wed, 09 Feb 2022 19:40:15 GMT

Sorry to dumb this all down but my search for an answer to the following question hasn't yielded anything. If I want to build a WAB, I need to (and can only) start with a "classic" web map - correct? I can't take a new "beta" map viewer web map and push that into a WAB?

Re: Experience Builder woes

jcarlson — Wed, 09 Feb 2022 19:46:45 GMT

You can take a new map and open it in WAB mostly just fine, the issue is that certain advanced features will not work, like fancy popups and newer symbology, or layer grouping.

Re: Experience Builder woes

ahargreaves_FW — Wed, 09 Feb 2022 20:27:06 GMT

Thanks @jcarlson. That's my issue - I have a beautifully styled "new" web map that now I need to throw out as it won't work in WAB. And every time I open a web map in "classic" mode I get told that the new map viewer is "out of beta!". Awesome, but those maps aren't backwards compatible.

Rant over.

Re: Experience Builder woes

JoshWhite — Wed, 09 Feb 2022 22:25:09 GMT

That is my biggest gripe about this whole thing. If you are not going to make something backward compatible at least make it capable of doing (or at least comparable with) what the previous software did.

Re: Experience Builder woes

jcarlson — Wed, 09 Feb 2022 22:33:09 GMT

I'm sure it'll get there eventually. EB is miles beyond what it was when it first released. I'm not exactly holding my breath for the more niche WAB widgets (Parcel Drafter!), but the rate of development has been pretty good so far.

Re: Experience Builder woes

JohnSasso2 — Mon, 04 Apr 2022 15:06:29 GMT

@JoshWhite I empathize. Herein lies the problem w/ Esri, in that they are pushing new platforms which are supposed to supersede existing platforms, which are NOT ready for primetime. In this case, Experience Builder w/r/t Web Appbuilder. Esri should never have pushed out EB until they made available at least what is available in WAB, and provided good, clear, thorough documentation for EB (having been an IT tech writer, the EB docs often leave me shaking my head). It is the same thing with the AGOL MapViewer, which is replacing MapViewer Classic.

I wish Esri would stop with the Force It Out Today, Fix Tomorrow (FIOTFIT) approach to their software. For a GIS developer like me, it is very, very frustrating. Sorry, but I had to vent!

Re: Experience Builder woes

DavidForbuss1 — Tue, 28 Nov 2023 20:00:54 GMT

I feel ya, having some pretty big issues myself with the url formatting. It went from a simple straightforward design that works, to a complicated "what in the heck does that even do?" approach. I really really need my map to be able to zoom to a feature from a url link in another software package (billing software in this case). Doesn't look like I'm able to do that in EB.