Input models not working: terms are entered but no descriptive fields

Question

input models not working. When I try to insert terms into the termbase from Studio, it inserts the terms in Spanish and English but it does not add the default fields (i.e., the purpose of the input model) with the defined information. This has been going on since last week. I tried restarting many times. At some stage I received the message "object reference not set to an instance of an object" and at some stage I had issues saving the xliff file...I kept getting a message saying that the file was in use elsewhere but the document was not open. I work in house and my colleague has the same problem. Any ideas? Regards, Tara 
 
 The message was "cannot access the file because it is being used by another process"

Paul · Accepted Answer

Hi Tara Browne , it's a CU so is rolled out via the automatic updates. You should be notified when you start MultiTerm. But I'll try to remember to post in here when we release too.

Paul · Answer

Hi Tara Browne

I played around with this a little and the only scenario I could make this work was using the Flags Layout in MultiTerm (not Studio) and apply the "Full Form Input Model". Unfortunately this seems to be a bug that we ran out of time to resolve for CU7 (Studio) and CU4 (MultiTerm) that were just released. We are working on Studio CU8 and MultiTerm CU5 to resolve this issue.

Regards

Paul

Paul Filkin | RWS Group

________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub

Paul · Answer

Hi Tara Browne 
 Please note this part of what I said: 
 Unknown said: Unfortunately this seems to be a bug that we ran out of time to resolve for CU7 (Studio) and CU4 (MultiTerm) that were just released. We are working on Studio CU8 and MultiTerm CU5 to resolve this issue. 
 MultiTerm CU5 is in Beta at the moment so we'll test this and make sure it has been resolved. 
 Regards 
 Paul

Paul · Answer

Hi Tara Browne , I'm afraid that's exactly what it means. Good news is the next CU was created specifically to resolve this problem and with any luck it will get released this week. At the latest next week in case of any showstoppers in testing. I can also make the Beta available to you if you like? It will mean you'd have to uninstall it once the release comes out but you could test the solution to make sure it will resolve your problem.

Paul Filkin | RWS Group

________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub

Paul · Answer

Unknown said: Would having the Beta version mean uninstalling the current version I have and trying the Beta version? 
 No. This is a CU (Cumulative Update or patch). But it would mean uninstalling the patch once we release the production version. 
 Unknown said: An upgrade means more payment right? 
 Not if you already have 2017. This is just a patch.

Paul · Answer

Hi Tara Browne , 
 
I'm not sure why you think could be related, we were talking about Termbases and now you mention Translation Memories? Are you sharing Translation Memories with other users? Or do you perhaps keep your Translation Memories on an external drive, or dropbox or something like that?

Paul · Answer

Unknown said: or if you had a solution. 
 I think the best solution is don't share the TM! It's not designed for this and if you wish to share TMs you need to apply a little trick. Take a copy of the TM so you have two. You write to one and read the other, so you them both on your Project Settings. Your colleague does the same but writes and reads to the opposite ones. This way you should avoid this locking error.

Paul · Answer

Hi Tara Browne , 
 
This is now available. You can find more details in this KB: 
 
 gateway.sdl.com/.../communityknowledge

Paul · Answer

Hi Gerald Dennett , please provide a sample of a termbase that behaves like this and some sample text to use for adding terms.

Trados Studio > 1. Trados Studio

Input models not working: terms are entered but no descriptive fields