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

ArcGIS Enterprise Sites 10.8.1 : Attribute table does not show anymore for Feature Layers

Martin1

We have an open data portal based on ArcGIS Enterprise Sites 10.8.1 (https://geo.fr.ch)

All used to work fine, but recently I noticed that the attribute table is not been shown anymore, when I click on Data in the detail view of a dataset (see below). I am not sure when this changed exactly, but I am pretty sure that nothing on the data side changed.

Is this maybe a bug that was introduced with one of the ArcGIS Enterprise updates? When I click on one of the features I can see the information from the attribute table for this feature, which means that it is likely not a problem with access rights. In Portal for ArcGIS it still works as it should.

Any help would be appreciated.

Trouver plus de publications taguées avec

Administration

Sharing and collaboration

Data and services

Accepted answers

Martin1

With the help of ESRI we finally were able to identify this behavior as a bug (registered as BUG-000144072).

The problem is that the basemap that I defined for the Enterprise Site was in a local coordinate system/projection (CH1903+ / LV95, EPSG:2056). While Portal for ArcGIS is able to handle that, this causes a problem for Enterprise Sites. The basemap is shown correctly, however the Site is then not able to access the data anymore (attribute table).

Till the bug has been solved, a workaround is to make sure that the basemap uses a more common coordinate system.

All comments

SzuNyiapTang

Hello Martin,

It might be due to one of the MIME type is not set properly in your Web Server.

For IIS, you will need to have the following MIME types registered.

extension	MIME/type	Description
.wasm	application/wasm	WebAssembly

Cheers,

Tang

Martin1

Hello Szu,

Thanks a lot for the tip.

However, I have checked and the .wasm extension seems to be registered properly (see below).

I tried removing and then re-registering (with a reboot of the server), but the result does not change.

Do not hesitate to share any other idea with me that comes to your mind.

Cheers,

Martin

Martin1

With the help of ESRI we finally were able to identify this behavior as a bug (registered as BUG-000144072).

Till the bug has been solved, a workaround is to make sure that the basemap uses a more common coordinate system.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

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