Jens Olaf Koch 

Hope you are well. Is this still something that isn't working as you would expect?
I assume you are talking about generating target files?

There was an issue when the path was copied using copy paste, and not browsing for a new location, but it was fixed in Studio 2022 CU1

Lyds

Lydia Simplicio 

Yes, same effect still: When generating target files I can neither choose the output directory nor the file version. The batch processing always uses a prior setting (= old directory, prior old selected version).

The same is true for new projects: Whatever I want to use, it sticks to the fixed output settings which I cannot change anymore whatsoever.

Very odd and annoying.

Jens Olaf Koch 

For the sake of clarity please allow for me to confirm what we do support:

1.  Export Files

This is managed as part of:

• default settings (File - Options) and would be a fixed location
• project templates - could be a custom location based on project template definition 

Regardless of it allows you to specify a path: 

2. Generate Target Files

This comes as part of Batch Task processing or simply "File - Save Target As"
The general rule is it saves the target native file in the project location. 



With all of this in mind, the only flexibility I see is if you are using the Export option.
Please can you confirm? 

The only other bit of flexibility I am aware of is that with 2022, there is an issue whereby you have Project A active in project view. You are working on Project B in editor view.
But when you are calling up certain features, it's not relevant to Project B as expected. In fact its Project A, as that is what is active in project view.

This may explain your impression of 

Jens Olaf Koch said:

Maybe some problem with broken project settings

If the latter proves to be true, then I am pleased to let you know that as of CU5 - this conflict of active project will be fixed.

I hope this helps clarify some points by which we can progress your post

Lyds

Lydia Simplicio

Well, there is only one project A open, not two projects A and B.

I will try again to explain what happens...

1. I have this file, it is a .sdlxliff file, no target file.

2. I have these project settings with the path ending with "04. Export aus Trados" and version set ti "current".

3. Then I export the file with the command from, the batch taks:

04. I export with these setting, exporting to a TARGET file, not the current version.

05. I end up with a file exported to the WRONG path ending "xx. Export aus Trados" (instead of "04. Export aus Trados" and the WRONG format (still .sdlxliff but not target file).

*

This is clearly not what to expect and seems unrelated to the project A/B bug being corrected in upcoming CU5.

Plainly said: I still cannot export to the path I want nor to the file format I want, and it doesn't matter whether I set my intended path and file format in the project settings or during the batch task – it always uses settings that I used ONCE before in this project. That is what I mean with: prior settings of the same project seem to stuck somewhere and cannot be overwritten anymore.

This is a serious problem.

Really no solution??

I now work on another project (book translation) and can STILL NOT CHANGE the target path for exports!!

Even if I delete the "stuck" path Trados always uses, it recreates it - no matter what I enter as correct export path. That means that NO export is ever written to the path I specify!

There must be a solution, right?

Please - help! :-)

*

I think that is either a bug or something is corrupted in a project settings file. Maybe I can edit them manually?

OK, I checked and find the current export settings in my .sdlproj file. They show the CORRECT path:

<SettingsGroup Id="ExportFilesSettings">
  <Setting Id="ExportLocation">F:\Kunden\O'Reilly\07 - Learning TypeScript\Textversionen\98. Export aus Trados</Setting>
</SettingsGroup>

Then why does Trados alwaysuses a DIFFERENT path?

Okay, after some digging I found the solution:

In the project batch settings for the current language pair was the wrong path. And although I changed that manually when exporting files, Trados always chose the path from the settings - which should not be the case.

So from my view it's clearly a bug. You just cannot offer the option to change the path while exporting when you are going to ignore that and use the one from the settings.

Okay, after some digging I found the solution:

In the project batch settings for the current language pair was the wrong path. And although I changed that manually when exporting files, Trados always chose the path from the settings - which should not be the case.

So from my view it's clearly a bug. You just cannot offer the option to change the path while exporting when you are going to ignore that and use the one from the settings.