Design your BAQ with parameters and get it working the way you would like.
When it is final, copy your BAQ and gut it down to just the top level. It doesn’t
even need to work at all, just must compile/save.
(No parameters in this BAQ)
Use Advanced BPM Update to override the GetList.
In the GetList BPM, pull your where clauses ( “Parameters” ) out of the
executionParams.ExecutionSetting and use the dynamic query adapter to call your original BAQ
with the parameters you parsed from the where fields.
Replace the rows in the called BAQ with the ones from the real BAQ and Bob’s your uncle.
Kinda Hokey, but if you need this functionality now, it can be finagled.
It grabs a certain number of records for paging (looks to be about 300 based on Dev Tools).
When you scroll past that, the parameter window comes up again (with no previous value) and you have to enter the same value to get the next 300 results.
Something I just noticed too… you lose the first 300 results after entering the parameter again… Neat. Nevermind. That was just a glitch, I guess. Shocking.
Lemme play with it. I’ve messed with the execution settings before in dynamic query REST calls, so I’m sure there’s a way to pass in the ExecutionParameter field.
Well–I have a half working option.
Only issue is it does not let me do virtual paging; still working that bit out.
You could set a larger page size if you know what kind of results you’re expecting, though.
Here’s the setup:
Make a placeholder view. Don’t make it an actual BAQ view or it will pull the params slide out.
I made my parameter a dropdown on the front page. Bind that to something and after the form loads, initialize it for the first call. I guess, strictly speaking, you probably don’t have to initialize it?
OMG Thank you this works really well, I just set my page size to 100,000 not sure if this will cause any issues. The query explodes all BoMs for a customer or product category, so it can be pretty hefty.
I have it working just statically right now plugging in a string in the executions parameters. I am a bit confused on how to get it to bind with my textbox.
These are all the parameters the BAQ has(Currently just using a textbox for Ordernum just for testing):
@hmwillett Thanks for the help! The solution does have a couple limitations on the user end. They can’t personalize the column layout, and the data can’t be exported to excel or even copied to excel.
Why not?
Are they grayed out? If so, click the grid in App Studio, go to properties > advanced and enable them. Or possibly properties > grid model > advanced.
I’m pretty sure in there somewhere are checkboxes to allow those.
I have been placing parameters into a UD table that I set aside for this purpose. . @hmwillett@Camren360 - I don’t know how to do all of the programming.
Steps are:
Create an updatable BAQ using UD11.
Filter the table so Key1 is equal to current user ID
Setup update to populate Key1 with UserID when you add a record
Make all other fields updateable execpt for Key2 thru Key5
In the BAQ(s) you want to use parameters on - pull in UD11 as a datafilter
create InnerSubquery with UD11 filter to Key1 equals Current UserID
Using a suquery filter or pull in UD11 into the query so OrderHed.Order is between UD11.Date01 and UD11.Date02
The added benefit is you can have multiple BAQs on a dashboard, all filtered by UD11.Date01 and UD11.date02
