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; } } }

Visualization data fail

SpatialSean

Have an interesting occurrence - and have created a few surveys now to test but all result in the same situation.

Each contain a Geopoint question where I've entered information both web form and iOS app. The points show when opening S123>my surveys> data. When I add the feature service to a new map or existing the points do now show. Opening the table results in "Error: Accessing data failed"

I've tried both Classic and New Map Viewer all same result now with multiple surveys. Surveys are not using any reserved keywords. Running connect v. 3.15.165

Thoughts?

Find more posts tagged with

Accepted answers

Richard_Purkis

Hi @SpatialSean. My current belief is that republishing changes the following setting in the item details in ArcGIS Online

I am still researching the issue but posting it here so that anybody else can check this setting first.

All comments

Richard_Purkis

@SpatialSean I have seen this issue when the ArcGIS Online subscription is brand new or converted from a trial. If you forget Survey123 for the moment, can you make a new feature class in ArcGIS Online and display data in the attribute table? If not, and you get the same error, you will need to raise a case to Tech Support.

SpatialSean

Thanks for the thought @Richard_Purkis - it is a new trial subscription but I just tested and can create new feature layers, see the attribute tables, and add to a map. Dashboards are working as well.

I'll still give tech support a quick call - it might be something on that end.

Richard_Purkis

Hi @SpatialSean. My current belief is that republishing changes the following setting in the item details in ArcGIS Online

I am still researching the issue but posting it here so that anybody else can check this setting first.

SpatialSean

Yes I ended up calling in and spoke with tech support. After trying a few things, we eventually discovered what you are showing above. To correct we disabled and re-enabled editing and were then able to allow editors to see all features. They logged it as a bug.

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.