Unexpected Changes to Base Fields in Updatable user developed Dashboards

Kinetic ERP
1

Hi,

I’ve encountered an issue with an updatable screen I developed for maintaining and collecting extra job data (mostly UD fields). Everything initially works as expected, but after some time, I noticed that when users update records (by entering values in UD fields), some base Epicor fields are unexpectedly changing.

For example:

  • ProdQty is being set to 0
  • JobReleased is being unchecked
  • Other unexpected field changes

Is this a known issue, or do you have any idea what might be causing this behavior?

Thanks

2

In the BAQ, double check the Query to Object and Object to Query Column Mapping tabs. Sometimes the BAQ auto-fills those incorrectly which can lead to strange results.

3

Thanks, Tom, for your attention. The strange behavior is that it works fine for a while, but it happens only to certain users!

Clearing user personalization resolves the issue.

Why does this happen, and what type of personalization is causing the issue?

I’m losing trust in UBAQs!

4

Personally, I don’t trust the UBAQ system and always write my own update BPM. I use the epicor BO’s, but I can control what’s set a lot better. With the stock updates, I’ve seen it update everything in the grid. This can be a problem if the data has changed since you refreshed your grid. Even if you don’t select that field to be updated, it will set it.

Once I started just making my own updates, following the traces, I’ve been a lot happier with how it works. There is a bit of a learning curve, but you don’t get the surprises with unintended consequences. You can do the updates with widgets if you don’t want to learn the C#, but it’s a lot faster once you just learn the C#.

4 Likes