As in: This post said it’s not possible, but I’m happy to hear that may not be the case.
I have one HTTP thing channel defined that grabs a handful of different properties in one shot. It returns a long string. e.g.
OID4.1.1=3&OID4.1.2=2&OID4.1.3=1&OID4.1.4=1&OID4.1.5=600&OID4.1.6=800&OID4.1.9=1&OID4.1.11=1&OID4.1.12=2&OID4.1.13=726&OID4.1.14=67&OID4.3.2.4=-2147483647&OID4.3.2.5=2147483647&OID4.5.5=7729
For each linked item, I use a item-specific regex to pull out the value, and cast it into its decimal precision. For example OID4.1.13:
s/.OID4.1.13=(\d)(\d)(?:$|&OID.*)/$1.$2/g
Grabs the value 726 and sets it to 72.6 degrees.
Note some OIDs in the string returned blown-out values (-2147483647) causing the aforementioned problem
Are you suggesting a transformation on the whole string at a channel level, before parsing the string on a per-item basis? If so, I could see matching/discarding those special 2^31 strings which would likely solve my particular problem. However it maybe wouldn’t help somebody (or me in the future) if trying to bound a value between x and y, rather than discarding based on a known outlier.
Can you give a code/syntax example of chained transformations?