How/where are EntryField objects displayed for Custom Terminology Providers?

I've built a custom terminology provider. The terms in the termbase have additional fields, such as gender, plurality, etc., which I have declared as instances of IEntryField on the EntryTerm object.

But where can I expect to see these fields?

And importantly, how can I present a term as being forbidden for us - i.e., indicate that a term should not be used?

The hitlist settings offer a preview showing the field values adjacent to the term's text...

...but my field values don't appear in the Term Recognition or Termbase Search panels...

Here is the object which is being displayed, showing that it's Fields property is populated...

What more do I need to do to have these fields presented in the UI?

1 Replies Latest Replies: 31 Dec 2018 8:30 AM by Florentina Caputa
  • Hello   ,

     You can look as a reference on how to display the entry fields in the IATE Terminology application found as open source app on the Github, in IATETerminologyProvider.cs class . I managed to display the entry fields by setting them up in the following places (all the below methods are defined in the IATETerminologyProvider.cs class):

    1. When creating the entry terms for the search result

    2. When setting the entry languages for the entry terms


    3. When creating the entry terms for the entry languages


    The method which generates the glossary descriptive fields based on the needed values looks like: (the method can be found in the same  IATETerminologyProvider.cs class)


    The descriptive fields which are shown in the Term Search/Term Recogniton grids and can be displayed using the Hitlist Settings option are defined as follows:

    (the method can be found in the same IATETerminologyProvider.cs class)


    For more references you can also check the documentation 



    The provider entry fields looks like in the below print screens in IATE Terminology Provider: (you can also setup the fonts of the entry fields from the Hitlist settings)



    With kind regards,

    Florentina Caputa