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

Layers with Subtypes not recognized as data in Experience Builder Dev Edition 1.16

Asrujit_SenGupta

After configuring the Exp Builder Dev Edition v1.16, we observed that certain layers do not show up in the Attribute Table or in the selectable list of data for Widgets.

The same Web Maps were working fine in ExpB v1.15 or when the layer is added directly, instead of via a Web Map. The Map Widget can see the data and Pop-ups are working fine.

A bit of troubleshooting revealed that only layers with Subtypes are showing this behavior.

So, our questions:

Has anybody else run into this issue with Subtypes?
Is this a new limitation in Exp Builder introduced from v1.16?

Find more posts tagged with

Accepted answers

Asrujit_SenGupta

Esri seems to have released a patch to fix this:

arcgis-experience-builder-sdk-resources/patches/1.16/patch1/arcgis-experience-builder at master · Esri/arcgis-experience-builder-sdk-resources · GitHub

Worked for us.

All comments

Asrujit_SenGupta

Esri seems to have released a patch to fix this:

arcgis-experience-builder-sdk-resources/patches/1.16/patch1/arcgis-experience-builder at master · Esri/arcgis-experience-builder-sdk-resources · GitHub

Worked for us.

Asrujit_SenGupta

Update: A new Bug was logged

BUG-000173271 - Unable to access the data that includes subtypes when publishing it as a map image in the Experience Builder Developer Edition version 1.16 while working fine in the 1.15

Asrujit_SenGupta

It does seem to work when the data is published as a Feature Service, and we use the feature Layer in the Web Map (fails with the Map Image Layer).

However, this is a workaround and not the expected behavior/solution.

BasWest

Hi @Asrujit_SenGupta

We are observing the exact same behaviour with our subtype layers in the table widget. We are in contact with concerning this issue. They informed us this should be working fine when publishing the layers with feature capability, but for us this has not solved the issue yet.

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.