True, but that’s hard to keep track of as well. Unique, yes. Easy to know where I used it, not really.
Also keep in mind we’re not always working with BAQ’s WE designed… so figuring out someone else’s schemes are often difficult.
For that matter, in many cases is could be a BAQ I DID design/build, but it was 6 months ago. I still need to do a deep dive to figure out what the hell I was thinking at the time and reconnect all the dots.
Only because it’s new…
@Mark_Wonsil should we merge?
https://epicor.ideas.aha.io/ideas/KIN-I-3756

DevOps was one BIG
idea because we had to limit entries due to the 50-vote limit at the time. I think smaller DevOps suggestions would have been better, and Epicor would probably prefer to roll out smaller and easier to manage capabilities than that one large idea.
I was talking about the notificatoin one.
Whew! At first, I thought I was going to have to call your wife…
Maybe… I can see some overlap. Probably some new capabilities with Collaborate as well… ![]()
There’s a little cross over with Kevin’s Konsole here too.
With work and documentation… “Pending Release” might never get here… ![]()
Karry on, Sir.
Currently the Production Yield Recalculation Process will only make adjustments that decrease the job quantities based on previous operations. It would be nice to also allow increases.
KIN-I-5407 - Allow Production Yield Recalculation to Also Make Upward (Increase) Adjustments
Wow, that threat escalated quickly!


Dedicated Account Login for Epicare Support - KIN-I-3445
Please vote if you are tired of having to grant access to each Epicare support agent who wants to replicate an issue in your environment related to your case.
Yeah, that’s not probably going to happen. I’m all for making it easier to do so but they aren’t going to accept the prospect of constantly being accused of messing with peoples’ data. Azure has a method of requesting access for a period of time, once it is approved, everything is logged. I could go for something like that.
Late to the party this week
This one is about ensuring we have a well maintained and clearly descripted Data Dictionary, with no Easter Eggs