# Vision Bug - Integer converting to float in indirect binding path

**URL:** <https://forum.inductiveautomation.com/t/vision-bug-integer-converting-to-float-in-indirect-binding-path/68769>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [January 19, 2023, 12:36am UTC](https://forum.inductiveautomation.com/t/vision-bug-integer-converting-to-float-in-indirect-binding-path/68769 "2023-01-19T00:36:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![WKetcham](https://avatars.discourse-cdn.com/v4/letter/w/c57346/32.png) [@WKetcham](https://forum.inductiveautomation.com/u/WKetcham)\
**Post date:** [January 19, 2023, 12:36am UTC](https://forum.inductiveautomation.com/t/vision-bug-integer-converting-to-float-in-indirect-binding-path/68769/1 "2023-01-19T00:36:36Z")

</div>

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.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/a/0ae5eda7533d87f0c622fe30890ccdbd919af972.png)

This is a screen shot of the binding:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/1/7149fb7c00f3e7811ca3a4cc32020924977dc8c0.png)

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.