This one is complicated and convoluted and not sure how to go about building it out. I need to either modify the std Epicor search filter (not possible I’m sure) or add a quick search to insert the results into the std Epicor report filter results. I’m trying to modify the std Sales Order Pick List report filter on Order to return a selection list which is different than the std version. My original thought was to add a custom button for “Order” and add logic which triggers a quick search that uses my criteria for “valid” options and then returns all sales orders in a tilde (~) delimited list which will be fed into the same field which is returned from the std search functionality. However, I’m not sure of the logic necessary to build out that delimited list or if it’s even going to work. Maybe there is a better way to accomplish the feat? I could build out my own version of the report but thinking that is fraught with omissions potential since I don’t have access to the std logic to see what it all does. The quick search seems to be the “simplest” route to follow but appearances can be deceptive (lol). Anybody try this or have thoughts?
Have you tried using a BAQ Search? That should be selectable when searching on the filters sheet of a print form.
The part that willbe tricky, is if the returnred data set is expected to have more than one key field. Fore example, a BAQ Search won’t work (without jumping through some major hoops) on a search the returns a OrderNum and OrderLine - like when searching for a line to add to a packer for a specific Order.
Calvin
I’ve recently built a BAQ for a different situation which returned multiple values (SO/line/rel) and then populated into the calling UI fields by using a custom search button attached to a BAQ search and a set of custom code - worked like a charm once I was able to get the knowledge from the epiusers collective. In this case I was thinking of doing the same but it’s slightly different in that instead of returning multiple key values for a single instance (i.e. SO/Line/Rel) I’m returning multiple instances (i.e. a list of SO’s). I’ve traced the process and already learned that the std search button returns a tilde delimited list of SO’s which populate into the filter grid so was thinking my custom button would utilize the same data field and (hopefully) the std logic would kick in and populate the filter grid with my values instead of the std button after my custom search was completed (probably still need to trigger it somehow - lol).