Table Widget loads slow on external facing application

[RichardFreer2]

I've created an experience that is using the Table(beta) widget linked to a Web Map, when creating, viewing from ArcGIS Online, everything works great.  Map and Table load as expected when viewing live.  Now I've published and shared the application for public viewing, and the map loads fine, but the Table takes forever to load with the data.  There are only 25 records currently, with 4 fields displaying with 21 total fields in the table.  I took the performance issue to be from alot of unused fields with very long fields, so I deleted all of those and still slow.  All of that was from a dataset hosted on ArcGIS Online.  So I created a brand new dataset, loaded the features from the original dataset, loaded it to our enterprise database, shared as service, added it to the original web map, reset all the settings in experience builder, and still slow.  I have another table on a different page in the same experience, and that loads quick.  So I don't know where to go from here.  Has anyone else had difficulty with performance issues (load speed) with the Table Widget?

[EmilyMcLeanACTGOV]

Hi @RichardFreer2 , 

I am having similar issues with the table widget, but I am also having issues with it loading multiple sheets featured within the one table. I find that the first sheet loads fine, but when accessing the other sheets, they don't load successfully the first time you view them. Instead I have found that I need to:

1. Open the Web Experience which loads the table widget with the first sheet showing (successfully) automatically
2. Select one of the other sheets.
3. Wait for the loading symbol to stop showing, leaving a blank table.
4. Select the first sheet again, and wait for the sheet to load successfully.
5. Return to the other sheet that didn't successfully load in step 3. 
6. Wait for it to load, where approx. 80% of the time it loads successfully. 

I have found that if the sheet still doesn't load following those steps that I need to refresh the page, and start the process all over again. 

Hopefully someone can share some insights into these issues. 

Thanks, 

[NourSalamJMT]

@RichardFreer2 I just ran into this issue myself and found out that when the Table Widget is within the hierarchy of the map element in the experience builder outline, the performance is significantly faster.

[BenClark]

Yep, I can confirm that it's significantly faster when nested inside the map. Unfortunately, I'm not sure how to have it in that same container yet not have it obscure the map, so I had to take mine out, making it slow to load. 😞

[NourSalamJMT]

We ended up using the collapsible table widget button rather than the whole table frame for just that reason @BenClark