Autobinding on null element with a null value

michal.friedrich · 2024-11-08T12:48:25.822Z

My database structure looks like that.
I have an option set of type of incomes. Income has related order. An order can be split into 3 parts so one master order can have 3 suborders. All of them can have different incomes which I group by income type.

So:

I have a repeating group where I list all orders incomes types (grouping).
I have 3-4 rows showing main order and it’s partial orders where I do a search for this row order and this grouping type income. I make sure I always have 1 income per type per one order/split order. So it’s not related to this issue ( I always watch the database).

That works.
I have small groups in this pivot table - where I look for an order and parent grouping. Inside I have an input. Every of those input can be adjusted with autobinding the found income value. It works in 90% cases. But it doesn’t work in those singular cases for absolutly no reason.

User I test it on is allowed to autobind on this element.
I can change the values of other elements (other incomes) and if I change the value in the database - it automatically refreshes to the proper value.

But somehow sometimes - the adjustment doesn’t work. I know it both from the database and from the search comparison (order incomes sum = split order incomes sum) that allows the confirm button.

What is the proper way to debug not working autobinding fields like that?

Update1: I identified that the issue comes from a bubble not being able to search an element where group option and order are added as a parameter. It shows null against the fact that the element exists in the database.

michal.friedrich · 2024-11-08T14:52:48.690Z

Update2: I assume the issue comes with problem with autobinding on a field with null data. Anybody experienced something like that?