Do not reload table widget while making edits, or at least don't scroll to the top

wayfaringrob

I've created an experience to make edits in a table widget. However, after each edit, the table refreshes, cancels my sort order, and scrolls to the top, which is fairly infuriating when you're trying to make multiple edits to a long table.

Stefan_Thorn · ‎06-13-2022

Hi @wayfaringrob

It is probably easier to connect to your table in AGOL or Enterprise via ArcGIS and do your edits.

wayfaringrob · ‎06-13-2022

@Stefan_Thorn I'm not sure what you mean. The table is a feature layer that lives in my ArcGIS Online organization.

Stefan_Thorn · ‎06-14-2022

@wayfaringrob

In ArcGIS Pro you can connect to ArcGIS Online and load the feature layer to a map or open the web map. If you have rights to edit you can edit your data in ArcGIS Pro similar to editing in ArcGIS Online but without that behavior.

Open ArcGIS Pro
Project > Portals > Add your AGOL Portal (forward slash must be added manually)
- i.e. https://<name>.maps.arcgis.com/
Sign in with your account
Now go to Map en in the right up corner of ArcGIS Pro you will see that you are logged in.
Open the Catalog Tab > Portal. Here you can see all the items in your portal that you have access to.
lookup the feature layer and add it to a new map.
Edit your data and not forget to save. after save the refresh your webmap and the data is updated.

Success!

wayfaringrob · ‎06-14-2022

@Stefan_Thorn I’m aware of that. I didn’t go to the trouble of setting up an experience builder app just for myself, though. This is an application intended to make editing user friendly and doable without a login or license.

ClayDonaldsonSWCA · ‎06-15-2022

a great idea. Editing the table is basically unusable right now with large tables. Since it has to reload after every edit

wayfaringrob · ‎06-20-2022

@ClayDonaldsonSWCA exactly, it's fine if you're making, like, one edit, but any more than that it really is unusable.

QuantitativeFuturist · ‎06-28-2022

@wayfaringrob I posted about this and was ignored, I guess they don't see it as an issue. Interestingly enough if you look at the code for the table widget in the JS API (in the sandbox) it DOES NOT refresh the table when making edits. My conclusion is that they completely botched the migration of the JS widget to experience builder. We are now looking at either dropping experience builder completely or recoding the table widget. Utterly ridiculous that the table widget made it past testing and into production because it's a complete failure and quite frankly an embarrassment to everyone involved.

wayfaringrob · ‎06-28-2022

@QuantitativeFuturist lots of half-baked stuff flying out of Esri lately. They are developing new things so quickly that it seems they are not testing them for quality, functionality, and ease of use. I agree with you, it's frustrating. And they make it so that the only recourse is to deal with cumbersome, time-consuming tech support that often refuses to log a bug or come here and scream into the void of developers in hopes that one of them cares enough to even suggest implementing the basic functionality that would make their software usable. It sucks.

QuantitativeFuturist · ‎09-02-2022

@wayfaringrob Update on this - I reported this bug at the UC, which they initially denied to my face!! Then they tried to blame it on the Javascript API implementation - which I demonstrated in the sandbox as working correctly. As I was reporting this bug, someone else came and reported the exact same thing. So they said it would be fixed in the next release (in case you're not aware, they are reducing the number of releases from 4 to 3, so have to wait even longer to fix bugs that were reported and ignored). The product manager/owner didn't seem to care at all about this bug and I think that's esri in general. We pay huge amounts of money and get incredibly lackluster service, the product manager for Experience Builder needs to be fired asap.

Your point regarding testing is completely valid - how is it possible to release software with obvious bugs and flaws and expect users to wait 4 months for a fix. They are not testing things properly and all the new shiny products in the world are worthless if you can't produce a stable core product.

wayfaringrob · ‎09-06-2022

@QuantitativeFuturist thanks for the intel. Yes, at a certain point, using something with issue after issue becomes really undesirable, especially when it takes a persistent (and in your case -- well-researched) village to find the time to convince the developers first that your issue is an issue and then that they should fix said issues. (All while trying to get whatever you were trying to do done.) We are fortunate to have staff in training for other web-based mapping solutions but in the meantime it would be nice if Esri refined their products substantially more than they're doing now. As a customer, it's mildly frustrating to shell out thousands per year to use something lauded as "class leading" that then breaks in your hands at a simple task.