nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Results View Contains Additional Tables compared to Main Feature Layer

RobertAnderson3

I have been troubleshooting an issue with the Survey123 website not loading a selected entry properly in the panel that pops up to show the details in the form view, it just spins endlessly. Through this we have noticed that the surveys that seem to have the issue all have an additional table in the results view.

Main Layer:

Results View:

Has anyone else encountered this? Any ideas what causes this?

I'm trying to figure out how this would have happened and I can't come up with anything unusual that I would have done, I simply share the results from the Collaborate tab on the Survey123 website, and it creates the results view automatically.

This explains why I had issues updating the view from the Settings tab in the item details for the view as well (the questions were all mismatched for the respective tables) though I feel that Survey123 publishing should do this automatically too.

Find more posts tagged with

Accepted answers

All comments

RobertAnderson3

The issue seems to have gotten worse, now the Data page as a whole just doesn't load for these surveys lol

Survey123 Website Data Page No Longer Loading on S... - Esri Community

RobertAnderson3

I swear I've had AGOL tell me before I can't create something because the name is already in use, but yeah I do suspect the itemID is what everything references.

Ah if only simple were so simple on a live survey being used regularly all day and tied into Power Automate and Power BI. But I have tried everything I can think of for a solution that isn't that, so I'll just have to find the right time to do it I guess.

abureaux

Glad you are starting to see some progress on this!

I'm sure the programs only look at itemId, so the technical answer is probably "not an issue". But still not something I'd be willing to trust. The human-level confusion alone I think justifies deleting one.

Seems like the simple solution is to recreate the survey from scratch after that geopoint change.

I feel like geopoints have been the culprit of a few AGO-specific issues recently.

RobertAnderson3

So I attempted to fix it by removing the null geopoint type question from my survey, republishing, deleting the results view, then re-sharing it.

This did not work, the new view continues to have extra tables. This seems to be purely because of the original created hosted table as opposed to a layer. It seems like the only solution is to publish a completely new survey (or potentially delete the hosted table and re-publishing to create it as a layer?)

I wonder, in AGOL, can you manually create the results view instead of having the collaboration settings on the Survey123 website create it?

EDIT: No you cannot manually create the view, the Survey123 website does not recognize it as the results view even when using the proper name. This leads to the odd situation of now having two items named the exact same thing in AGOL, which seems like an issue?

RobertAnderson3

In contacting Esri Support, after much digging, they have found it appears connected to BUG-000147659 for ArcGIS Online (esri.com)

The stakeholder or results view layer created from the ArcGIS Survey123 Collaborate tab generated a duplicate table in ArcGIS Online.

A published survey with a map question with the field type set to null, Survey123 Connect publishes a hosted table instead of a hosted layer. Then when you share the survey results, it creates a duplicate table in the results view layer.

RobertAnderson3

Haha no worries! I figured maybe you were on vacation or something lol.

That's a good point, it is odd that it is 0 and 1 like that, though I wonder if it's because it's the primary feature layer and then the rest are related tables, it would always be put as the higher number?

When I try the update view, it shows me the 4 expected tables, but the fields are like:

Mowing Work Orders (0) --> Mowing Work Orders (0)
assetRepeat (1) --> Mowing Work Orders (1)
employee_repeat (2) --> assetRepeat (2)
vehicle_repeat (3) --> employee_repeat (3)

So the fields don't line up, I have no idea what it will do if I try to proceed with updating the view, I'm worried to try when it's live data lol.

I figure it was a publishing error somewhere along the line, but in the Survey123 environment, I haven't seen anyone else complain about it though so.

I am planning on deleting and resharing the results views, I have done that on one of the surveys I have already and that's how I found it as a solution, I just wanted to try and find the cause as well.

abureaux

Now I feel bad! I will have to scroll through the list again lol.

The numbering is basically an OID starting at 0 and is generated when an item is created. Given that, I would guess that the duplicate layer was created when the view was originally created. Otherwise, I'm not sure how they would be 0 and 1, respectively. If it happened later, I'd expect to see the original as 0 and the new one as 4.

We actually had an odd thing happen late last week with those ids. A layer was (I assume) republished by someone, and the layer Id changed from 0 to 1, breaking our Web Apps. Once I realized what happened, I had to jump through some hoops to restore widget functionality. Not quite the same issue you are seeing though.

Maybe just recreate the View an monitor for now?

RobertAnderson3

No idea, there were a few things I posted in the last little bit I was surprised not to get a notification from you on haha

All of my surveys are hosted in AGOL not Enterprise so it might make a difference, all are published via Connect, but the views would be created automatically when picking the sharing settings on the S123 website. I have no idea how it happened, or when honestly, which makes it harder to track down the exact cause. A hiccup is definitely possible, they're numbered differently though so it should have been able to tell what was there?

abureaux

How did I miss this question?Just found it via your Idea.

I checked my View layers, and I don't see any additional layers/tables (Enterprise 11.3).

However, I create all my view layers from the Portal rather than the S123 Website. Not sure that would have any affect though. Maybe there was a hiccup in the communication between servers resulting in a duplicate layer?

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.