Lori

It is a bit complicated to explain and I like the depth you are going into here... haven't seen this many questions around how to work with Multiterm for a very long time!

First of all, and Loredana Stoia can correct me if I'm wrong, when you add new fields at the term level they always apply to all languages in the definition even if you use MT Convert and specify otherwise.  This applies to MultiTerm and also to Language Cloud.  So if you do this in MT Convert:

It will look like this in MultiTerm:

Similarly it will look the same in Language Cloud as you have discovered.  In MultiTerm you have additional capabilities to control how these are used.  So for example, I can create a custom Layout that will always only show what I want and in the order I want:

Mine now looks like this (changed background colour, defined the order and what actually displays irrespective of what entries I have):

I can also create an input model to control what is allowable when adding new terms:

Looks like this when I add a new one (exactly as you'd prefer to see):

So... all good so far.  But when it comes to using the new "Default Layout" in MultiTerm or the new Language Cloud Terminology, none of these things are possible.  You can only control the order of the layout and what can be added if you are using the older MultiTerm technology.

I guess Loredana Stoia might be able to tell you what plans we have for improving this in the future, but for now I hope this explains why you can't do what you have attempted?  Or she'll explain why I'm completely wrong... which would be good :-)

Thank you Paul for your explanation. The sample termbase you made was funny.

Just wanted to point out that in my example, the Note-zh field was missing altogether in the new termbase.

I thought what I wanted to was pretty straightforward, but looks like it's another rabbit hole...