Last “Frideas” (two weeks ago) it seemed like the consensus is that people here love bugs in Kinetic so that they can fix them and have a day job.
I’m still fighting this concept. If you all love re-creating reports for Epicor, well have fun.
But I just cannot shake the idea of patching all the holes in the Posting Engine - if you even find them. I definitely get tired of explaining to accounting why nothing ever fully reconciles or that the transaction hierarchy has an error on nearly every page.
On that note - here’s a pic of the 2025.1 guide. It takes all the way till page 3 to find an error. Still cannot spell CST correctly.
Have I ever reported it? Nope. Ummm… have you read this thread? I’d have to submit it as a product enhancement and wait for enough votes.
This may seem like a silly example, but I include it because it’s easy to explain.
The more complicated ones are the real challenge. We find them and know that they are legit problems, but reporting them goes nowhere. 2 votes, 7 votes, expired. These are not fun or cool and they have zero impact on writing C# code, so no one cares to vote for them. But they do matter to the real people that use the software and the people trying to run their businesses who couldn’t care less about the REST API.
There just needs to be a separate dedicated team for financial bug reporting, specifically. People who get it. If it’s not about Application Studio or BAQs, no one listens today.