I’ve looked around and I do not see anyone else reporting this. If I can get a little validation I’ll submit to Epicor, or if it’s just me, I’ll wait until I patch up to the next level and see if it still exists.
Here’s a short video of the behavior because it’s hard to explain. The same field value change occurs when changing the operation cells too.
And this is an older BAQ from 10.1.500 that went through the upgrade, if that matters. I have not seen this behavior on queries created in 10.2.300.
Thanks guys. It’s getting so much worse now that I’m editing a slew of BAQ’s because of a process change. Aggravating. And now I’ve found where an external query (change of datasource) reset ALL of my table criteria back to field=company, operation is ‘=’, and expression = null.
Anyone report it to Epicor? Any hints as far as how to avoid it as much as possible?
Anyone got a name at Epicor of who I can stalk about this?(besides the guy @Bart_Elia is bringing to the Vegas meetup?)
@ckrusen - seems to be whenever you alter a condition in any way. I first noticed it like @josecgomez says, but it breaks when you are changing the operation value too…
There’s no avoiding it @MikeGross I’ve gotten used to looking at the my field after every change and no I didn’t report it to Epicor because #Lazy
But if you do send me your ticket number and I’ll join in the chorus. Or better yet here @Rich please fix this?