Is sorting related records in web app builder possible?

4151
29
10-03-2016 07:17 AM
ThomasFurcron
Occasional Contributor

First being able to edit related records using web app builder is AWESOME!!https://community.esri.com/community/gis/web-gis/web-appbuilder?sr=search&searchId=33647200-6910-4c2...

Now for my question. 

I set up in ArcGIS online a webmap that has a feature class and a single related table.  Under the configure pop-up i checked show related records and under sort options i set up the sort based on a date field.  Now when I open this map in Collector on the ipad it functions properly, showing the related records in descending order by date.

Arcgis Online sort set up

But when I use web app builder to set up the the editor widget it does not honor the sorting based on the web map it is created off of.  Is there another way to sort this data in web app builder?Web App Builder not sorting

29 Replies
MichaelTownshend
New Contributor III

Which is insane as this is precisely what the bug fix was supposed to address.

Time to open another case with support.

0 Kudos
NataliyaLys
Occasional Contributor II

I agree. And on the ESRI support site it says that it was implemented? 

MichaelVolz
Esteemed Contributor

I have been working with ESRI technical support on this issue for several weeks and the excellent support specialist was able to replicate this issue and has created another bug BUG-000119084 so I would recommend calling technical support and getting attached to this bug so you can track it's progress and ESRI knows it is impacting multiple endusers.  I would wait until next week to get attached to this bug as it is probably not in the system just yet due to the holidays.

MichaelTownshend
New Contributor III

I was on the phone with support demonstrating our issue when this post notification came in.  Thank you... I've forwarded on the bug number.

0 Kudos
MichaelVolz
Esteemed Contributor

It was a weird case as the support specialist at first was unable to replicate the issue.  Did you get far enough into the case with technical support for them to replicate the issue for you?

MichaelTownshend
New Contributor III

So far Support was not able to reproduce the error as they had only tried using a service Hosted in AGOL.  We were on a screen share today and I walked them through my process, ArcMap 10.5.1, Enterprise GDB in Oracle, Shared on our ArcGIS Server and then registered in AGOL.  When I illustrated that the sort config was not honored in WAB he said that he would test again using a service not Hosted in AGOL.  So, it sounds like our environments could be pretty similar.  At this point I don't know if he will continue the attempt of replicating the issue as I have forwarded him the bug number.

MichaelVolz
Esteemed Contributor

I was very grateful that the ESRI technical support specialist was persistent with the case as I thought it was going to be an unreproducible case.  Does your data get updated on a regular basis (daily, weekly, etc.)?

Have you tried reproducing this workflow in Pro just to see if you can move on from ArcMap for this process?

MichaelTownshend
New Contributor III

Hmmm,   interesting.  These data are updated nightly.  

I have not attempted to reproduce this error with Pro since this service is hosted on our own ArcGIS Server and we are using AGOL not Portal.  My tech tried using Pro and was not able to reproduce the error but again, that was with a Hosted service.

0 Kudos
OliviaDeSimone
Occasional Contributor

I got my case attached to BUG-000119084 today.  This forum was very helpful.  Hopefully they will resolve it soon!

MichaelVolz
Esteemed Contributor

Now that ESRI has Experience Builder in beta testing to be released in a few months into production, will bug fixes like those mentioned in this thread ever be fixed in Web App Builder?  Or will these bug fixes just be incorporated into Experience Builder as ESRI's way of pushing organizations to Experience Builder?

I'm thinking of suggestion bugs associated with address locators that were identified but never resolved in ArcMap.  Migrating to Pro was the only way to get past the suggestion bugs.

0 Kudos