I’m starting to convert my classic dashboards to Kinetic dashboards, and I know just enough to be dangerous.
If I have more than one tab in the kinetic dashboard and those tabs use input parameters, then there’s a slide out panel that prompts for the input parameters for multiple tabs, back to back. I also had the classic dashboard set to not auto-load on open, so that the user has to click the Refresh button on the tab where they want to see the data. (I’m using the word tab loosely, because in Kinetic, what used to be tabs in classic are pushed into the same page, but in separate collapsible frames. AKA cards?)
The Kinetic dashboard tries to load all the tabs at once, and so there are multiple input parameter prompts in a row, and no indication to which tab the prompt applies.
What is the Kinetic way to handle this? I skimmed through the Application Studio manual and didn’t see anything that addressed this, and I’m not sure if any of the training videos covers this scenario.
I have been using a user defined table to hold parameters that other BAQs use.
The key is to use the Key1 and other fields to manage the parameters by user.
Basic setup is:
Create an updatable BAQ for UD11 that allows adding records.
Set when the a new record is created, Key1 is populated with the CurrentUserID.
Filter the UD11 in this BAQ that Key1 is equal to currentUserID.
In the BAQs that you want to have parameters put in a subquery with UD11 filter to Key1 is equal to currentUserID.
the other subqueries can then be filtered based on other fields on the UD11 table. For example OrderRel.ReqDate <= UD11.Date01 and OrderRel.ReqDate>= UD11.Date02
On the dashboard I put a grid view (not a tracker) that shows the Date01 and Date02 fields. Instruct the use to enter the dates and hit save, then hit refresh.
Here’s a dashboard to demonstrate how you can capture parameters and feed to multiple BAQs
Grant why would you have a dashboard showing Order Backlog along with Open Purchase Orders?