# How to retrieve input proxy properties in a programmable filter ?

**URL:** https://discourse.paraview.org/t/how-to-retrieve-input-proxy-properties-in-a-programmable-filter/5993
**Category:** ParaView Support
**Tags:** python
**Created:** [December 6, 2020, 7:53pm UTC](https://discourse.paraview.org/t/how-to-retrieve-input-proxy-properties-in-a-programmable-filter/5993 "2020-12-06T19:53:19Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Mohamed\_Abdelkhalek](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mohamed_abdelkhalek/32/4384_2.png) [@Mohamed\_Abdelkhalek](https://discourse.paraview.org/u/Mohamed_Abdelkhalek)
#### Post date: [December 6, 2020, 7:53pm UTC](https://discourse.paraview.org/t/how-to-retrieve-input-proxy-properties-in-a-programmable-filter/5993/1 "2020-12-06T19:53:19Z")

</div>

For example if I have a clip filter with type box, that I use to crop an image volume (unstructured grid).

If I use this clip filter as an input to a programmable filter, I only get the underlying vtk object, which is an unstrucutred grid. How can I obtain, the proxy propertes of the clip such as (Rotation, Position, etc.).

Generally, is there a way to query the proxy properites of inputs to programmable filters ?

---

<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: [December 7, 2020, 9:22am UTC](https://discourse.paraview.org/t/how-to-retrieve-input-proxy-properties-in-a-programmable-filter/5993/2 "2020-12-07T09:22:21Z")

</div>

You can’t.

What are you trying to achieve ?

---

<div class="post-metadata">

### Author: ![Mohamed\_Abdelkhalek](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mohamed_abdelkhalek/32/4384_2.png) [@Mohamed\_Abdelkhalek](https://discourse.paraview.org/u/Mohamed_Abdelkhalek)
#### Post date: [December 7, 2020, 8:34pm UTC](https://discourse.paraview.org/t/how-to-retrieve-input-proxy-properties-in-a-programmable-filter/5993/3 "2020-12-07T20:34:16Z")

</div>

Thanks, I realize that, I actually was able to sort of circumvent this limitation by passing arguments to the programmable filter via eval and string escaping in the macro and using string replace to pass arguments to programmableFilter Script property.