Aller au contenu principal

Control field order for tabular interfaces

Commentaires

2 commentaires

  • Victor Catalán

    Hi Zorba,

    thanks for raising this! You're absolutely right that field order is important for usability and often a customer-specific requirement.

    Just to clarify:
    In VertiGIS Studio Web (VSW), for most interfaces such as search results, identify, and query results, the field order is not arbitrary or strictly alphabetical — it is typically derived from the WebMap configuration, specifically from the popup settings of the corresponding layer or table in the Esri WebMap.

    ➡️ That means you can define the field order, formatting, visibility, and aliases directly in the WebMap, and VSW will respect that configuration.

    📄 More info on how to configure pop-ups in a WebMap (including field order): https://doc.arcgis.com/en/arcgis-online/create-maps/configure-pop-ups.htm

    So if you adjust the popup configuration in your WebMap accordingly, it should reflect in your VSW app as expected.

    0
  • Zorba Conlen

    Thanks for the reply Victor. I see what you mean. I think there is a gap however. The field order and other configurations can be done in the ‘fields list’ content type in the webmap, but what if your popup does not use a fields list? We generally prefer to format our popups with text content type only. With this type of configuration, there is no way to specify field order. 

    I'd argue that having control of the field order in a tabular view should not be dependent on what type of content one chooses when configuring the webmap popup. 

    Also, there remains the issue with field order for data in a relationship class.

    Thanks

    0

Vous devez vous connecter pour laisser un commentaire.