Advice on Large Dashboard Development

Kinetic ERP
1

With the advent of App Studio and web based …conditions…
Here is my task : Rebuild one of our largest dashboards to be Web-Browserable( there is a new word) . There are a lot of Updateable BAQ’s running behind it. There is 1 top level BAQ that drives the rest of them , ECO GroupID that “Pubs” to various “Sub” Grids.
The first couple of “Sub” baq’s I added I changed the baq’s to be Parameter driven. The 3rd one I just used the Wizard generated stub( User defined Actions) method _Get ----to filter the results to fill the Data view------Edit below.
The old Classic Dashboard just filtered on the top ECO GroupID to fill the grids

Now the main question, Should I continue to convert the working BAQ’s to Parameter driven or will the Filter on the _Get action execute filter server side ?

Looking for best practice …

Thanks in advance for your input !

EDIT, Use the Parent Child Relationship in the Dataview

Dean

2

I’m interested what others say, but I’m finding parameters mostly more reliable so far, at least when I can’t be sure how much data will be involved. I use the filters for the simplest cases.

That doesn’t count as best practice, though, I’m pretty sure. Partly because that still feels like a moving target.