# Selectors in combination with duplicated block names

**URL:** https://discourse.paraview.org/t/selectors-in-combination-with-duplicated-block-names/11455
**Category:** ParaView Support
**Created:** [February 21, 2023, 9:35am UTC](https://discourse.paraview.org/t/selectors-in-combination-with-duplicated-block-names/11455 "2023-02-21T09:35:37Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![pcrepier](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/p/f4b2a3/32.png) [@pcrepier](https://discourse.paraview.org/u/pcrepier)
#### Post date: [February 21, 2023, 9:35am UTC](https://discourse.paraview.org/t/selectors-in-combination-with-duplicated-block-names/11455/1 "2023-02-21T09:35:37Z")

</div>

Hello,

I am in the process of converting my post-processing scripts to make them compatible with PV5.11.  
I now hit an interesting problem: I have multi-zone tecplot file that paraview reads just fine, but some of the blocks have duplicated file names.  
So when I specify the required selector to extract a specific block, I do not get one of the blocks, but multiple ones.  
I there a possibility to work around this ? (Yes I can change the naming in the file, but that won’t have any effect for a year, so that will be fixed, but I have to work with this for a year …)

Previously I was using the block indices directly, so there was no issue about this.

Thanks in advance!

---

<div class="post-metadata">

### Author: ![Tox](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/t/8e8cbc/32.png) [@Tox](https://discourse.paraview.org/u/Tox)
#### Post date: [June 26, 2023, 3:59pm UTC](https://discourse.paraview.org/t/selectors-in-combination-with-duplicated-block-names/11455/2 "2023-06-26T15:59:40Z")

</div>

@pcrepier 🙂 Did not see your question before, but I have exactly the same one: [Reading zones with identical names using TecplotReader into Paraview - ParaView Support - ParaView](https://discourse.paraview.org/t/reading-zones-with-identical-names-using-tecplotreader-into-paraview/12118). It appears to be a bug to fix and I made it into an issue: [TecplotReader issue with similar named zones (#22144) · Issues · ParaView / ParaView · GitLab (kitware.com)](https://gitlab.kitware.com/paraview/paraview/-/issues/22144). Hope it will be fixed in the near future…