Kinetic Bindings - Seeking Enlightenment

Kinetic ERP
, ,
1

I just spent an embarrassing amount of time troubleshooting something I thought I had a grasp on, but turns out I do not. As such, I am now seeking some understanding. All examples here are using BAQ as a source.

Short version of the story
Created new dashboard in application studio with a single dataview and single panel grid. Works great. Add second dataview and everything is now broken. Can repeat on demand.

However, if I use the wizard (which is getting better) and create two dataivews and panel grids in the wizard, everything works as intended. After manually adding my criteria, my publish and subscribe functionality even works. Fun note: If you hit the guided setup on the panel grids again at any point after the initial wizard created them, it also seems to break.

I get this super helpful error message.

image
image784×992 61 KB

Now, on the the part where I seek clarification.
There seems to be about 142 different ways (ok this might be hyperbole) you can bind data to a grid in application studio. After dealing with the above issue, it is now clear that I don’t understand what the differences are and when each should be used.

By my count there are actually only 4 places that could be defined. In the properties of the Panel Grid:

  • Data: EpBinding (can reference dataview)
  • GridModel: EpBinding (can reference dataview)
  • Provider Model: EpBinding (can reference dataview)
  • Provider Model: BAQ ID (reference native BAQ ID)

The rules seem to maybe not be 100% consistent as it seems to change which ones you should use based on how many dataviews you might have. What works for a single, might not work where there are multiple.

Is there some simple guideline that explains when/why you choose to use some of these over others?

3 Likes
2

try to open DevTools console window and check red messages there. It must be more descriptive. Undefined just means that error message does not correspond any expecting format and panel cannot show it correctly.

1 Like
3

I deleted the broken versions out of frustration, but I can re-create them and try that to see if the error at least provides better details.

I wasn’t really griping all that much about the error message itself as my lack of understanding how the different flavors of bindings are intended to work.

4

It may be not even related for your changes.
Personally I often get this message when auth token is expired and client cannot connect to server. Server returns 401 error in that case, but client has troubles to process it correctly and switch back to login page.

1 Like