I am an avid reader of the Epiusers forum, and I want to thank you all for your support. With your assistance, I have resolved a plethora of issues with Epicor. However, I have encountered a peculiar problem with Epicor Kinetic 2024.1 that I have been unable to resolve. I am writing this topic in hopes that someone can help me.
In Epicor Kinetic version 2024.1, I have created a non-editable grid that pulls data from a non-updatable BAQ. This grid is located within a sliding page that opens during the textbox search click event. The purpose of the grid is to enable users to search for a part number and select it using grid selectors, allowing the selected value to be set in the textbox.
To facilitate this selection functionality, I added a Calculated_Selector column to the BAQ, which serves as the selector field in the grid. This enables me to identify the currently selected record within the DataView condition widget.
The setup works well, allowing users to search for and select part numbers. However, a problem occurs when users select a record and quickly scroll through the grid; this action triggers the dashboard to call UpdateBAQ during the scrolling process.
I should note that when a record is selected in the grid, the RowStatus column is added to the DataView, and the record is marked with a āUā symbol. This behaviour is similar to that of an updatable Dashboard, but since the BAQ itself is non-updatable, I do not understand why it would call UpdateBAQ at all.
If anyone has insights or suggestions regarding this issue, I would greatly appreciate your help! Thank you.
Interesting. Ok, Iām past my helpfulness, as Iām not up to speed on the kinetic stuff yet. I use that method (make a checkbox) in classic all the time, but you have to make the BAQ updateable to make it checkable. When I do that, Iāve needed to put a dummy update method in the BAQ to stop errors from popping up.
What errors is this causing? If you didnāt set a BO in the ubaq, there really isnāt anything this can update anyways.
I agree, it does not actually update data and it cannot since to make BAQ updatable you need specify update BO method.
This BAQ is not updatable hence no BO method to call, but UpdateBAQ call returns an error that causes an ugly error slider to appear during grid scroll, and even worst, is that grid remains broken afterwards and does not load data, user needs to refresh application for it to work again.
Updatable BAQ is hard to maintain in Kinetic.
For example, if you add a new column to the BAQ and forget to add it to the Kinetic Dashboard, during update, the Kinetic will drop data from the record. This issue does not exist in classic but alive and well in Kinetic.
I have a lot of cool ideas that involve grid selection functionality, I would like to implement them without creating an additional updatable BAQs.
Some of those ideas do involve updatable dashboards, but this erratic behaviour of the Kinetic scares me a little and I want to understand why is this happening, so that I can reliably counter it.
The dashboard I am creating right now is very simple, and it requires simple and reliable solution. if I cannot resolve it reliably right now, this issue will propagate and create more problems for me in the future.
I opened a ticket around february for this issue, it was at another company so iām not sure what the outcome was. But I got a PRB for it - a dashboard linked to a uBAQ will drop any columns not included in the grid. Itās bad - if you set up a uBAQ on UD01 that includes only Company and Key1-5, and shortchar01, if your ubaq includes only those fields, and you update shortchar01, you lose anything in shortchar02,03,04,date01,02, etc. etc., itās nice!
Yes, client must provide all values, included in mapping. Otherwise update will set the defaults.
So what is the case number or what do you have from support?
