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

Alphabetic Table View vs Feature Service

Alex-Santos

There are some datasets we've set a specific order to the attribution, within the service, so they appear similar in hub. The new UI is now reordering them alphabetically. An example is the EDI dataset. Our map service places the DATAINVENTORY_ID first but explorer places it fourth. It looks correct in AGOL. How do we ensure hub honors the attribute order we set in our services?

Encuentra más publicaciones etiquetadas con

Accepted answers

Anonymous User

As a follow-up, we released this change today. Your tables should now retain the same field order as the service. Let me know if anything isn't showing as expected.

All comments

Anonymous User

Thanks for the feedback. We are in the process of changing the sort for data tables to preserve the field order set in the service. I'll let you know when this change is released.

Anonymous User

As a follow-up, we released this change today. Your tables should now retain the same field order as the service. Let me know if anything isn't showing as expected.

Alex-Santos

Thanks Patrick. I can see the tables are showing the same field order as in services.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

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