Configuring Attributes

Attributes are defined as a collection in the entityTypes section of the configuration file.

Attribute Order in the Profile View

The order of the attributes in your JSON file determines the order seen in the entity type profile view.

The order of the attributes listed in your JSON file dictates the order seen in the profile view of that entity type. If in your L3 you reference the uri of an attribute defined in a lower-level, then it will become the top-most attribute in the facet. If you wish to modify one or more attributes defined in a lower-level but which to maintain the order you must mention all the attribute uris so that L3 has the complete list mentioned within it.

This example illustrates how you can reorder attributes:

{
  "uri": "Configuration",
  "referenceConfigurationURI": "Configuration/_vertical/life-sciences",
  "entityTypes": [
 {
   "uri": "Configuration/entityTypes/Company",
   "attributes": [
     {
     "uri": "Configuration/entityTypes/Company/attributes/Name"
     },

     {
       "uri": "Configuration/entityTypes/Company/attributes/Specialities",
       "dataLabelPattern": "{SpecialtyType} - {Description}",
       "attributes": [
         {
           "uri": "Configuration/entityTypes/Company/attributes/Specialities/attributes/Specialty",
           "lookupCode": "SPEC2"
         }
       ]
     }
   ]
 }
  ]
}

In the example above, the uri for the Name attribute is listed first . All other attributes appear in the UI after the Specialties attribute. If we wanted to move more attributes before Specialty, their URIs would appear before Specialties.

Note: In addition to all Registered Levels needing abstract=true at the top Data Model level, each entity type you want to inherit from must have its abstract attribute set to true if you do not want it to appear in the list of entity types to create in the menu. For example, Party and Individual are usually hidden this way but not HCP and HCO.