Batch Delete option with a filter not working with Trados Studio 2021

I would like to delete TU units belonging to a given project. I have added the term 'To be deleted' in my TM Source File custom field for the specific project. I have added a filter called 'To be deleted' in my TM. I have performed a search in my TM to make sure my filter works properly, and it did:

Screenshot of Trados Studio showing the Perform Search feature with a filter 'To be deleted' applied, displaying matching translation units.

I have clicked on Batch Delete, and I've added the filter I've created:

Screenshot of Trados Studio's Batch Delete Filter window with 'To be deleted' filter selected from the dropdown menu.

After clicking on Finish, I have got this result:

Screenshot of Trados Studio's Applying batch delete script window showing the process running but no translation units being deleted.

Any ideas why the Batch Delete feature is not deleting any units when the Peform Search feature does actually find the units using the same filter?

Thanks very much in advance for your help!



Generated Image Alt-Text
[edited by: Trados AI at 8:27 AM (GMT 0) on 29 Feb 2024]
emoji
Parents
  •  

    I believe this is a problem that should be resolved in SR2 due for release in due course.  The first beta for this version was released into the beta community today so we can test this and make sure.

    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

  • Hi Paul,

    Is the fix expected to be released soon?

    I am also having a similar issue with Trados Sudio 2021, version 16.0.1.2917.

    I have thousands of misaligned segments that I try to batch delete in a TM whose size is about 1.6 GB, with the following filter (meant to include all segments created in the specified interval):

    Trados Studio filter settings showing conditions for 'Created on' dates with specific timestamps.

    When I run the batch delete, it instantly gives this:

    Trados Studio message indicating the batch delete script is running but has deleted 0 translation units.

    The outcome is exactly the same if I use this SourceFile filter instead (while it does give thousands of results when I perform a search in the same TM with the exact same filter):

    Trados Studio filter settings showing a condition for 'SourceFile' containing a specific file name.

    From what I understood from previous exchanges on this forum regarding similar issues, it seems to be related to the size of the TM, but as you may guess, anyone who has been using Trados Studio for years will most likely get at least one huge TM, which at the same time increases the odds of having misaligned segments in it which would require batch delete. So, if the issue is really just the size of the TM, the fact of knowing that is not a solution: it definitely requires a fix, or at least a detailed workaround procedure.

    I will try to find my own workaround (for instance, exporting the existing TM with the same filters, but with the “NOT” boxes checkes, then reimporting it in an empty TM), but that will be much longer, hence the need for an actual fix of what seems to be either a bug or a shortcoming.

    That being said, thanks for everything you do for this community, Paul!

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 8:27 AM (GMT 0) on 29 Feb 2024]
  • I haven't tested this yet, but I believe it has been addressed in the new version of Trados Studio due shortly.  There was a lot of work done on these kind of features in this release.  I can add you to the Beta forum if you like so you can test and validate?

    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

    emoji
Reply Children
  • Hi Paul,

    Thanks for the follow-up. If I could, I would gladly participate in the beta testing, but I use Trados Studio on a government computer on which any software installation is strictly controlled (i.e. impossible until it is officially pre-tested and approved by IT).

    That being said, if I could be added to a beta forum, I would still be interested, just to be informed of what patches and updates might be coming up.

    Oh, and by the way, the filters I mentioned above also don't work when trying to export parts of my 1.6 GB memory, and the same is true for at least one of my colleagues, so the problem is not just with the batch delete: it seems to be with any filter used for a relatively big TM (except for the research function, which works well even with a filter).

    In any case, do you think you could let us know here when one or several of the filter bugs are corrected? If necessary, I could then push for the latest update to be installed on our government computers (since we don't usually have the latest ones; for instance, the latest version available to us now is 16.1.4.4184, while another user on this page was already using 16.2.9.9198 three months ago).

    Thanks again, and have a nice day!

    emoji
  • if I could be added to a beta forum, I would still be interested, just to be informed of what patches and updates might be coming up.

    I have added you, so you can check the release notes for each release.

    the problem is not just with the batch delete: it seems to be with any filter

    Correct.

    In any case, do you think you could let us know here when one or several of the filter bugs are corrected?

    If you have a support contract then the support team will notify you when bugs you have reported have been resolved and in which release. We can't guarantee to do that in the community, but you'll find details in the release notes of each release.

    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

    emoji