File export: Trados does not use chosen path but another path used before

Question

Hello, 
 
 when I export files and I chose during the batch task the export path to whatever path (I tried different, existing ones) , the export goes always to the same fixed path I used the first time I exported files in this project. 
 Also any change to the version I want to export is not reflected, it exports always the current version of a file, not for instance the target file when I highlighted a file in .sdlxliff format and tried to export the target language version. 
 In other words: Changes to the settings during the export process are not working, although they get saved and can be seen the next time. But Trados just does not use them but a prior, fixed version of the settings. 
 Maybe some problem with broken project settings (I had a Trados crash a couple of days ago in this very project)? 
 * 
 This is Trados Studio Freelance 2022 with latest updates/SR on Windows 11 with all latest updates. 
 I re-started Trados, re-booted the machine - no change. 
 * 
 Thanks in advance for any ideas! 
 Best regards, 
 Jens Olaf

Lydia Simplicio · Answer

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 · Answer

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

Trados Studio > 1. Trados Studio

File export: Trados does not use chosen path but another path used before