Performance of updateable dashboard, Best practices

I just created an updateable dashboard for purchasing to control the purchase direct, link to contract, make direct, scrap and one UD fields. I have the BAQ to allow multiple rows to try to reduce the amount of times he has to save. We are noticing though that it takes 10-20 seconds or more to save. I’m wondering if there are some best practices to make the saving from and updateable dashboard faster. Are there certain fields that should be included in the query that would help the system find things faster? Should I look at adding parameters instead of using a dashboard filter? (I’m wondering the amount of rows that are returned make the save take longer)

Any tips would be appreciated.

interesting, I did some testing on my machine, take 2 seconds to save max. I’m wondering what the difference is?

What version of Epicor are you running? We have noticed similar issues in UBAQ in 10.1.600. Some clients are much slower than others. One thing we’ve observed on a slower machine is the OS version and .NET framework (Windows 10 with .NET 4.7+). To clarify, we haven’t tested this on multiple machines so the cause is still unknown just wondering if your slow machine has similar .NET / OS combo.

We are 10.1.600.5. I don’t really know where to look to test those things. I do know that the other user has an older machine.

We are implementing ERP10 and are currently on 10.1.400.20 we created a UBAQ for updating sales price lists. The only 2 tables that are in the BAQ are PriceLstParts and PriceLst, The price field is set as updateable, there are no customisations or UD fields, yet it takes on average 40 seconds to save the record.

We have raised this with support and they have not been able to find the cause and have passed this on to product development, it seems specific to our database but they don’t know why, there is nothing special about its configuration.