# Session Props, View Props and direct component property binding

**URL:** <https://forum.inductiveautomation.com/t/session-props-view-props-and-direct-component-property-binding/74254>\
**Category:** Ignition\
**Created:** [May 29, 2023, 5:48am UTC](https://forum.inductiveautomation.com/t/session-props-view-props-and-direct-component-property-binding/74254 "2023-05-29T05:48:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Faisal\_Shaikh](https://avatars.discourse-cdn.com/v4/letter/f/3ec8ea/32.png) [@Faisal\_Shaikh](https://forum.inductiveautomation.com/u/Faisal_Shaikh)\
**Post date:** [May 29, 2023, 5:48am UTC](https://forum.inductiveautomation.com/t/session-props-view-props-and-direct-component-property-binding/74254/1 "2023-05-29T05:48:24Z")

</div>

Hi,  
I want to know the pros and cons of using session or view props instead of using the component property binding directly to another component

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [May 29, 2023, 6:11am UTC](https://forum.inductiveautomation.com/t/session-props-view-props-and-direct-component-property-binding/74254/2 "2023-05-29T06:11:26Z")

</div>

Session props are available to the whole session and can act as global variables and a simple means of passing data from one view to another. I use them regularly for things such as date range selection that is to be applied across views.

View props can behave similarly. Advantages include:

- All the variables can be located in the same place.
- Bindings to the view props means that bindings continue to work when components are moved up and down branches in the project tree. For example, wrapping a component in a container will move that component down a level and break any bindings to or from that component. Binding to the view props avoids that.
