Hi Rosanna Lithgow 
I guess this intended behaviour as Translation Units (TUs) of a TM are always seen as higher quality translation source compared to concordance or fragement matches.
Studio displays only fragment and concordance matches, if no match can be found in the TM(s) of your project:

File > Options > Editor

I think, the best way to achieve what you want, namely having MT from your customer displayed as well as using your TMs for exact, fuzzy, concordance or fragment matches, is to ask your customer not to send you a tmx but rather a pre-translated sdlxliff or even better a project package in which the sdlxliff is pre-translated with the customer's MT engine (means the target text column in the editor is already filled with the MT outputs of your customer).

If you continue working with the tmx export, the only way to dinstinguish between your own TM matches and the ones from your customer is to work with field values and filter penalties. However, this only shows you where the matches come from in the Translation Result Window, you won't receive concordance/fragment matches this way.

To use the filter options:

Add field values in the tmx import when creating your customer's MT TM:

Then, set filter penalties in the projects settings according to the field values you added before:

Test if you need to set the condition to "NOT" as filters work reverse.

A concordance search can always be performed manually by highlighting the source text or parts of it and pressing F3.

Regarding the order in which matches are displayed in the Translation Results Window: You can choose TM order in the project settings by moving them up/down using the blue arrow:

By moving the TMs up/down you can decide which matches of which TM should be displayed first/second, etc. in your Translation Results Window.

If you'd like to see only your TMs and therefore see concordance/fragment matches of your TMs but still use your customer's MT outputs, I'd recommend asking for a pre-translated document.

I hope this helps.

Best

Seraina

Thank you, Seraina. I will try the field values and penalties suggestion on my next project. 

The interesting thing is, fragment matches show up as suggestions as I type, so they must be "hiding" somewhere.

I think the green and yellow squares indicate a fragment match, right? In the segment where this suggestion shows up as I type, no fragment match show up, just the MT in the translation results window, or I can find the term by doing a physical concordance match (F3). I find it very strange and frustrating that I can't get to see the fragment match that is obviously there somewhere. It should be obvious that these matches are more important than a machine translation and should be given priority by Trados.

Rosanna 

Thank you, Seraina. I will try the field values and penalties suggestion on my next project. 

The interesting thing is, fragment matches show up as suggestions as I type, so they must be "hiding" somewhere.

I think the green and yellow squares indicate a fragment match, right? In the segment where this suggestion shows up as I type, no fragment match show up, just the MT in the translation results window, or I can find the term by doing a physical concordance match (F3). I find it very strange and frustrating that I can't get to see the fragment match that is obviously there somewhere. It should be obvious that these matches are more important than a machine translation and should be given priority by Trados.

Rosanna 

Hi Rosanna Lithgow 

It actually is always there in the Editor view:

But if a TM match is found, it automatically jumps back to the Translation Results Window (red arrow).

This is default behaviour.

Studio only jumps to the Fragment Match Window if no matching TU can be found the TM. In your case, there is always a matching TU form the TM as you created a TM which contains a match for every segment. Therefore, Studio will never jump into the fragment section automatically.

The only way to pin the Fragment Matches Window is to right click on the window and set it as "Floating":

You can now move it wherever you like (e.g. to a second screen)

or integrate it in the Editor View by moving to the position you'd like to have it displayed:

Result:

If you later on whish to change the Window Layout, click on Reset Window Layout under the View tab:

Maybe this helps.

Best 

Seraina

PS: Your MT is preceived as TM by Studio as you enter the MT outputs in a TM. The source of TUs in a TM doesn't matter for Studio to be detected as a TM.
Therefore, I'd still consider asking your client to provide a project with a pre-translation including the MT outputs.

No, the fragment matches are NOT there, that's the problem. When I click on the fragment match window I get the message "Exact match found [i.e. the MT] (No fragment search performed). This is the behaviour I want to change. I want it to perform a fragment search AS WELL as showing med the MT translation in the translation resaults window.

This is with "Search for fuzzy matches even if exact match is found" ticked under Project settings - translation memory - search:

Not sure if minimum match value is correct, but I get the same behaviour with it set to 70, so it doesn't seem to make a difference.

Rosanna

Hi Rosanna Lithgow 

No need to become upset. I'm only a user trying to help; I'm not a developer or customer manager from RWS.

As said, as long as you have exact or 100 matches from a TU, there won't be performed a Fragment Match Lookup.

Therefore, I'd suggest to either use the penalty feature or to ask your client for a pre-translate.

Best

Seraina