We recently upgraded a client to v8.1.22 and just noticed an odd behavior a couple of screens with indirect bindings that had not existed pre-upgrade.
The indirect binding combines a TagPrefix and TagSuffix (both string custom properties) with a RecipeIndex (integer) sandwiched in the middle. When Vision evaluates the binding it is first converting RecipeIndex to a float. The screen shot below shows the three custom properties used in the binding on the left and console output on the right shows the binding error.
This is a screen shot of the binding:
The other odd thing is in runtime this binding error only occurs on about half of the objects with this exact binding. Also in designer if I open the existing binding and just hit "Ok" it updates correctly but in runtime it reverts to erroring (it also errors if I reopen the window in designer).
Anyone else seen this or any thoughts from IA?
Thanks.