Why ever use an expression transform instead of an expression binding?

Ignition
1

i get map and script transforms, those add new capacity

but why ever expression transform?

2

To combine an indirect tag binding with an expression. When you don't need the tag value itself for any other purpose.

(I pretty much never do this, as another use for the tag value is almost inevitable.)

4 Likes
3

Well one project I saw that they chained multiple expression transforms to do increasingly more operations on each’s output… :face_with_raised_eyebrow:

4

I would use my Integration Toolkit's alternate tranform() for this--less overhead.