Customs properties in data glossary are displayed in a random order

[melquior-chaves-wcq]

The custom properties defined for a business glossary term are displayed in the web interface from different order than they appear in the yaml file.

In order to reproduce the issue, try to import the yaml file attached and compare the order of the custom properties to the order displayed on the web interface.

Expected behavior
The order of the custom properties displayed in web interface should match the order in the yaml file.

Screenshots
See attachements.

Desktop (please complete the following information):

• OS: macos 15
• Browser Chrome
• Version 0.14

CorpAvgCost.txt
*** this file has been renamed to .txt from .yaml in order to be attached.

[aviv-julienjehannet]

It is not only for glossary terms. It is general and nested custom properties are affected too.
For example, when using documentation forms, prompt order will be lost when custom properties are showed in the properties panel.

[chriscollins3456]

hey @melquior-chaves-wcq thank you for calling this out! this is something we'll be looking into and will definitely get back. We'll think about options for ordering properties in general

This issue specifically references custom properties while @aviv-julienjehannet is referencing structured properties - structured properties will always be displayed first in the properties tab then custom properties.

Question for @aviv-julienjehannet - i know you mention prompt order on the form being an order you would expect, but since you can add structured properties outside of the forms context I think decoupling the ordering between those two would make sense. how else would you expect the order of properties in this tab to be ordered?