# Pipeline browser name filtering

**URL:** https://discourse.paraview.org/t/pipeline-browser-name-filtering/2689
**Category:** ParaView Support
**Created:** [October 4, 2019, 8:55am UTC](https://discourse.paraview.org/t/pipeline-browser-name-filtering/2689 "2019-10-04T08:55:12Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![david.k](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/d/65b543/32.png) [@david.k](https://discourse.paraview.org/u/david.k)
#### Post date: [October 4, 2019, 8:55am UTC](https://discourse.paraview.org/t/pipeline-browser-name-filtering/2689/1 "2019-10-04T08:55:13Z")

</div>

Hello,

I have multiple layers in my pipeline browser loaded from separate \*.pvd files. It works just perfect when the data are loaded manualy (by drag and drop, file(layer) by file). However just after I save the state of the project into the pvsm and load it again I loose my naming of the files and the numbers in filenames are replaced by dots, so instead of original names  
Profile01vel  
Profile02vel

I got after reloading the model

Profile…vel  
Profile…vel

What is bit anoying for further sharing the model.

Is it somehow possible to turn of the filenames grouping for the pipeline browser?

Many thanks  
David

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 4, 2019, 8:58am UTC](https://discourse.paraview.org/t/pipeline-browser-name-filtering/2689/2 "2019-10-04T08:58:20Z")

</div>

I would suggest you to avoid using numbering but instead use lettering if possible.

---

<div class="post-metadata">

### Author: ![david.k](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/d/65b543/32.png) [@david.k](https://discourse.paraview.org/u/david.k)
#### Post date: [October 4, 2019, 9:04am UTC](https://discourse.paraview.org/t/pipeline-browser-name-filtering/2689/3 "2019-10-04T09:04:17Z")

</div>

Hi Mathieu,

thanks for your instant reply. Unfortunatelly, the naming convention is already given and highly depending on numbers. (btw. the naming in the example above is just a very simplified example)

David

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 4, 2019, 9:16am UTC](https://discourse.paraview.org/t/pipeline-browser-name-filtering/2689/4 "2019-10-04T09:16:32Z")

</div>

Actually, I’m not able to reproduce. could you provide simple files and steps to reproduce the problem ?

---

<div class="post-metadata">

### Author: ![david.k](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/d/65b543/32.png) [@david.k](https://discourse.paraview.org/u/david.k)
#### Post date: [October 4, 2019, 9:38am UTC](https://discourse.paraview.org/t/pipeline-browser-name-filtering/2689/5 "2019-10-04T09:38:10Z")

</div>

Hey Mathieu,

find attached two sample files. The flowchart I follow:

1. Load the files separately by drag and drop into the pipeline browser

2. save the state into a \*.pvsm file

3. move the folder onto another computer or folder

4. load the pvsm using an option of defining the path in the new folder (Search files under specified directory)  
note: the naming stays OK if go with the option “Use File Names from State”

5. names in pipeline browser are simplified as numbers are no more visible

I’m using Paraview 5.6.0 (same happening in the 5.7.0)

David

[sample.zip](https://discourse.paraview.org/uploads/short-url/wufEtfNLBQUSGY0jGmaPP21Nj7d.zip) (11.2 KB)

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 4, 2019, 9:49am UTC](https://discourse.paraview.org/t/pipeline-browser-name-filtering/2689/6 "2019-10-04T09:49:37Z")

</div>

I reproduce. That’s a bug. Nice find.  
I’ve created an issue here :  
[https://gitlab.kitware.com/paraview/paraview/issues/19363](https://gitlab.kitware.com/paraview/paraview/issues/19363)
