BAQ specified in the Grid Provider Model populates multiple unrelated DataViews

Hello everyone,

I have encountered a very unusual issue in Epicor Kinetic, and I hope someone has resolved it before.

When creating a dashboard using the application wizard in Epicor Kinetic versions 2024.1 and 2024.2, if you set up two grids powered by the same BAQ, the application wizard will link the two grids together.
For example, if you expand Grid 1, it will populate both Grid 1 and Grid 2; similarly, if you expand Grid 2, it will populate both Grid 2 and Grid 1 at the same time.

The strange part is that both grids have no connection to each other, aside from referencing the same BAQ in the provider model. They have completely different data views set in the Provider model’s epBinding. Yet, when you expand either grid, the Kinetic UI populates both dataviews.

I just ran into this yesterday. I just decided to make one pcg with two views instead. Probably somebody smarter will have a real workaround . . .

Currently, I have identified two potential solutions to this issue:

  1. Remove the affected DataView from the EpBindings on either of the grids.
  2. Delete one of the affected DataViews and create a new one from scratch.

As Alisa mentioned, we can also make use of views instead of separate grids.

These approaches resolve the issue, but if anyone knows the root cause, please share your insights. I would greatly appreciate your help.

1 Like