Here’s an example video of how to do a BAQ dataview.
BAQ Dataviews are a great way to view related data onto a screen in Epicor. If you can link the data on the screen to the data you want to display in a BAQ you can display it. They are faster and more flexible than FKVs or embedded dashboards.
All kidding aside whenever possible use BAQ DataView they are fast and easy and work just like any regular DataView in your form.
So you get all the EpiMagic and the events that come with it.
I hope Josh doesn’t mind me sharing his screenshot, but what Josh is refering to is he actually uses UBAQ BPMs to manage the grid, no client side code (or atleast minimal). It becomes it’s own isolated business logic grid.
You know the UDXX Wizard Generated Code… its much cleaner as a BAQDataView, and can easily be re-used in other screens.
Good catch @bordway.
The publisher subscribe doesn’t like not having a row. I think embedded dashboards have a similar issue.
This cleans it up. I added an EpiViewNotification to look for a change of the order number and applying a second filter to the dataview. This also clears the view when clear is pressed.
I must not be doing something correctly. If I have just one binding it works just fine. It’s when I try to add the second one in, it just seems to ignore one or the other. In this case, it’s returning the part with all of the customers listed. It doesn’t matter if I put CustID first or second.
I’m adding it to the part tracker. I have a custom EpiDataView that I store the customer data in, I have bound textboxes as well to make sure they are properly populated. The data refreshes when I put a new part in, but it doesn’t care about changing the CustID (or CustNum) field. I have a feeling I’m misunderstanding something which would explain it.
I did try that. The query is pretty intense, so I have changed it to a parameterized query where I just get one row back. It takes 1/10th the time. I was just hoping I could figure out something about this because this way is much easier.
I just had an interesting problem with a BAQ Dataview that was subscribed to two fields.
On a UD screen I am storing CustNum_c and ShipToNum_c and retrieving information about the shipto with a BAQ dataview. Everything worked great 90% of the time, but occasionally while moving through records the BAQ data view would not refresh correctly. It didn’t seem to be related to any specific records since sometimes I could leave a record and return to it and it would be ok. I have two other BAQ daviews with a single publish/subscribe relation that work 100% of the time. My work around was to change the my baq dataview to use the SysRowId of the UD table for the publish/subscribe relation.
Has anyone seen similar issues with subscribing to multiple fields?