Latest Contributions by MichaelMorisette

@NairiSevajian  Thank you for the response.  However, I feel it missed the mark.  We were very aware of the incident as it happened, and that Esri was working on it.  The purpose of this thread was by no means to report it, but to both pressure and help Esri to do better going forward. To call the Jun 26 incident "minor disruption" or "performance issues" is an understatement.  Esri botched the update, and ArcGIS online was straight up down.  Even as we came back online, there have been lingering issues caused by the update that we've spent hours with technical support on.  I feel Esri needs to take more ownership and initiative on issues they cause. Some general (hopefully helpful) takeaways I have both from this thread as well as our organization's experiences over the last several years. When a major system outage is noticed, please do communicate the fact with us Send a mass email out, or at least update the AGOL status dashboard to be something more descriptive of the issue at hand "go Through Technical Support" is not a working solution when the technical support doesn't get the information to the right people in a timely fashion (product development, AGOL operations, etc.) This wasn't always the case, but has been gradually getting worse over the years There have been countless instances where we call support, spend hours and even days of our time with busy work they give us, just to find out the problem was on Esri's end all along and that they might fix it with the next full release if they feel like it Work internally to improve the overall quality of the product, and convey to us you are doing so For example, CentralSquare (another enterprise suite we use) routinely report metrics on how they are doing this at their conference plenary sessions The number of support cases submitted in the first place, not just their time to resolution, is a good KPI for this from what I've seen Less technical support cases opened meaning the product is getting the bugs ironed out as well as becoming more intuitive ... View more

...and this is all before we discover all the application breaking bugs (and occasional "intended behavior").  We'll then call technical support who will give us the runaround and have us spend days of work doing arbitrary troubleshooting steps having nothing to do with the issue at hand.  We close more than half of our support cases out of frustration and/or when we find a workaround the hot buggy mess that has become the norm for most Esri products. Honestly, we're starting to move more and more workflows off the Esri framework and into our other enterprise applications wherever possible.  As web applications become increasingly mission critical to our everyday operations, we need stability above all else.  Esri tools are very powerful when they do work as intended and we'd love to continue using them.  There was a time when I swore by Esri products.  Please get it together and turn things back around, Esri. ... View more

Hi @Jianxia What is the best mechanism to get bugs on the development team's radar? I noted several issues from the previous 1.16 release that don't seem to be addressed.  New features are always welcome.  However, as web GIS is becoming more and more critical to our organizational needs, we really need a robust product above all else.  EXB in its current state is not offering this. ... View more

Absolutely needed.  Why is this not there already as with every other enterprise software in existence? ... View more

Agreed.  We really need this widget to fully migrate away from Web AppBuilder. I get that there's an instant app with the functionality, but it makes no sense why it isn't being included into Experience builder given how the product is being advertised as a "kitchen sink" of sorts.  Our userbase is accustomed to being able to use a single application for everything. ... View more

Hi @Jianxia There are a few major issues, that appear to still be missing from the roadmap, and that are preventing Experience Builder from being a suitable replacement of Web Appbuilder for our organization. Public Notification widget missing entirely (we really need to have this in EXB versus a separate app as our userbase relies on it being in our main map viewer) There seems to be a bug (as of the latest release of Developer Edition) where the basemap scales aren't getting detected properly, which results in a pixelated basemap as well as some scales not showing up entirely (this is not an issue in WAB, or any other Esri product that I've noticed) Some widgets (Geoprocessing and Elevation Profile that I've noticed) prompt users to login even though the underlying services they are hitting are publicly accessible and don't require a login in any other app we use them with Also a bug? Any thoughts for any of these? Thanks ... View more

*Accidental Post* ... View more

Adding the AppID to the config.json did the trick!  Thanks for the help. I guess I didn't read the manual. ... View more

Thank you for reaching out @BernSzukalski.  For whatever reason this post came into my web search when trying to figure out how to switch templates and I felt the need to vent some frustration online.  I will follow up via Email as suggested about the specific concern. If nothing else, this personal level of customer care is what always makes it great in the grand scheme of things. ... View more

It is not a suitable replacement as it currently stands.  There are several widgets we rely on that are still missing in Experience Builder.  Additionally, it doesn't appear possible to switch templates after app creation which completely defeats the purpose.  All the "express mode" appears to be is a stripped-down version of full mode, and not at all how AppBuilder functioned. If you choose to reinvent the wheel, then it's on you to provide a stable and functional equivalent before retiring the old app; this is the bare minimum in the software world and doesn't seem like it should be asking much. ... View more

I've ran into this bug after upgrading from 2.8.x to 2.9.x.  Using the saveACopy(aprxPath) workaround worked for me as well. ... View more