# Perspective Components' Value Binding

**URL:** <https://forum.inductiveautomation.com/t/perspective-components-value-binding/83563>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [December 28, 2023, 1:37am UTC](https://forum.inductiveautomation.com/t/perspective-components-value-binding/83563 "2023-12-28T01:37:48Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [December 29, 2023, 1:38pm UTC](https://forum.inductiveautomation.com/t/perspective-components-value-binding/83563/14 "2023-12-29T13:38:20Z")

</div>

The Engineering Unit binding, on a component custom property, looks like this:

 ![20231229_0835](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/a/aac5ff1c34b6fc81f80388ba0622c92400a04a17.png)

The Format String binding is similar, also on a component custom property.

Then the text property binding (I used a label component) would look like this:

 ![20231229_0834](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/d/8dbd7a698c19cbe069c7571354b04c30c0c6442b.png)

No `tag()` function!

Everywhere in a UI you **think** you need a `tag()` function, train yourself to split off a custom property with an indirect binding.

---

_[View the full topic](https://forum.inductiveautomation.com/t/perspective-components-value-binding/83563)._
