Designer Bindings Don't Update

I am trying to debug a perspective screen for a customer of mine. The view has a pretty basic structure with several input parameters and a few custom properties that are running some querries and other scripts. However, when I look at any binding, it does not actually update to the value it is bound to.

For example, I created this test custom property and bound it to the "enable" parameter which is just a simple input parameter boolean.

image

You can see that the binding does not update at all. This is happening on every binding on the view.

I've restarted the designer several times and this issue persists but only with this view. My only thought is that there's some long process running that is interfering with the binding update execution, but I've dug into all the components on the view and there is nothing that jumps out at me that could be doing that.

It does seem to be working correctly in the session though so maybe it's designer specific? I've never ran into this issue before. Anyone have any ideas of where to possible look for issues or anyone else that's seen this before?

Nothing comes to mind that would cause that behavior, so I've got a few general questions:

  • Does the view have any scripting (either on components or as a property change script)?
    • If yes, what are they doing and where is the gateway relative to your designer (localhost, local network, remote via VPN, etc)?
  • Anything useful showing up in the gateway logs (Status>Diagnostics>Logs) or running scripts (Status>Diagnostics>Running Scripts)?
  • How complex is the view? Can you try rebuilding it piece by piece to isolate the root cause?

It does have some limited scripting. I've already went through and systematically disabled pretty much everything on both the view itself and all of the subviews. None of that made any difference. I also went through every binding, transform, component event, message handler, etc on the screen to try to find something that would be causing it and there is nothing that stands out.

Nothing shows in the logs either as far as I can tell.

I was hoping to avoid your third suggestion since the view is pretty complex but it looks like that might be my only option.

I'm assuming you've ruled out the most obvious thing and restarted the designer already?

Understandable, it's not a fun process but it should definitely get you an answer.

Maybe someone else has another suggestion, but rebuilding it is probably what I'd end up doing

Is restarting the gateway an option? Just another quick sanity check

Yea I've tried this as well as restarting my local environment.

I did try this too as well as having another developer open the view. Same issue so I've ruled out it being something with my local environment. Just called support and they suggested doing what you also suggested and just rebuild the whole thing so I guess that's what I'm going to do. Yay :upside_down_face:

It probably won't help but worth a shot. Try creating a new View, copy the JSON of the original View (Shift+right click on the original View, Copy JSON) then paste it over the top of the new View (Shift+right click on new View, Paste JSON).

Alternatively, do the bindings start working if you edit them and press OK? I've seen bindings very very occasionally lock up - must be corruption of the View and usually after an upgrade - and they need to be edited and saved to kick back into gear. Usually only happens to 1 or 2 bindings in the View though, and for the record, it's usually only 1 or 2 Views that is affects as well.

I tried copying the JSON to a new view and the issue persisted on all bindings. Editing them also does nothing. Additionally, if I create a new parameter and try to bind something to it, it shows up in the property selector tree but then the evaluation of the property binding shows "Bad Not Found".

I also just went through and systematically deleted every component, binding, script, etc on the screen until there was nothing left and the bindings continued to not update. Call me very confused.

Are you already in touch with support? If this is reproducible, we would definitely like to have this view in house to test against.

Yea, I reached out yesterday. They are just as confused as I. Just sent them a gwbk so hopefully will get some info soon.

1 Like