Anthony Rudd

I have no idea what you are looking for, or how it looked before it changed, but do you just need to use these features to open the missing pane and ribbon then lock them into place?

Thanks Paul. This solved my problem. As usual, you have the solution. But I have another question related to TBs: 

I have added 2 "Term level" fields - they do not appear when I add a new entry. What am I doing wrong? 

Anthony Rudd

Fields don't appear as open edit points automatically, but you should be able to select them and open them to add your data.

A better approach however is to create an input model where you can set what gets added automatically, and open the edit point. I'll illustrate without the default mode as it's easier to see the difference.

For example... without the input model:

With an input model:

You set this up in the Termbase Management view:

There's always a "gotcha"

An input model is possible only at the Entry level, and in this case the Next button is greyed-out (I have added the Project field at the Entry level)

Anthony Rudd

Indeed there is ;-)  This time you just haven't added the nodes that are needed to be able to add the fields you want.  I added a couple of fields to my definition at the term level.  To add them to my model I need to add the appropriate node from my list:

So first I might add "Any Language" for example and then I can select the ones that go on the term level:

I found your YouTube presentation for this topic - and as you said there "a piece of cake" - provided you know what to do. The associated data model is now clearer, 
And to think that I only got involved in this topic because I want to use CheckTerm with my TBs that do not have a Usage field, something that it does not support and I could not persuade the developers to permit "Allowed" as default.

I found your YouTube presentation for this topic - and as you said there "a piece of cake" - provided you know what to do. The associated data model is now clearer, 
And to think that I only got involved in this topic because I want to use CheckTerm with my TBs that do not have a Usage field, something that it does not support and I could not persuade the developers to permit "Allowed" as default.

MultiTerm is quite an interesting product because it is actually quite an extensive tool with a lot of capability and flexibility.  But you only really find out about this if you work as a terminologist or start trying to use some of the features to solve a particular problem.  Fortunately I have some of the old manuals on a bookshelf (from when we used to print them) and it's a godsend for when you forget how to do something!

It's nice to know that I am not alone in sometimes forgetting things!