There’s a few posts on the Before Image stuff that might be helpful:
But basically the before Image snapshot (from progress) was at one point adapted into the SQL Uplift and its how epicor does the “Field Changed from X to Y” it just means you get the same row twice one with and one without changes. Sometimes in BPMs you have to even do it yourself like in the above example.
Then Epicor literally does a little LINQ query comparing the Before and After fields to see if it changed. This was done automatically for you in the classic client via the Adapter (you didn’t have to do the before image injection yourself).
I guess in the web client they aren’t injecting the before image row on all the calls automatically as @Olga pointed out this probably should be reported and I suspect Epicor can change the way those Field Changed from X to Y widgets work to do lookups on the Db.
However for a BAQ that would be tough since the entire BAQ dataset is in memory it isn’t a single table it is a “view” generated by you so they’ll probably have to change the web client to send the BI at least for UBAQs otherwise I’m not sure they’ll ever be able to reliably tell that something changed (or didn’t)
I honestly think it may be a bit of a technical limitation (at least for a while) and we’ll have to work around it. (Assuming that is in fact what is happening)