Just curious…
7 Likes
My real goal is to gauge if that is normal. The “not to brag” was just to make people chuckle.
How many of those are “Waiting on Customer” (you)?
“Problems” are never “waiting on Customer.” I do have some “Cases” that are “waiting on Customer”
thank you… I missed that in your title post. PRB not CS. Wow… 42!
I can’t remember the largest number we had open, but it was big enough to download into excel and review on a weekly call with support. You can always ask for a point person and scheduled review calls - I believe they still do that.
Jenn
5 Likes
good idea, thanks for the advice!
Thank you for being a beta-tester!
1 Like
Myself and one other person are a two part team working on an Epicor implementation for 4 companies… We started in regular Epicor, and had to learn that - before migrating to kinetic and learning kinetic. I would have to go back and look… but we have found so many issues and glitches and bugs that have been updated or solved. I don’t think we have any open issues at present… but this new update will surely create a firestorm.
I honestly don’t know how you can spend that much time with the Epiccare Portal reporting cases, I find working with them exhausting when I have 4 or 5 cases open?
5 Likes
We have one case that we have uploaded DB copies twice on and it’s been open for almost 2 months now. Another one, that it’s like they picked from a hat sending us data fixes that haven’t worked and now need a different copy of our DB because not part of the same group as the one referenced… It’s a never ending cycle with them and with new people in support you have to make sure you test all of their suggestions and feedback.
Do I smell a little 
starting?
3 Likes
Ditto.
Yeah, I mean I used to have a lot, but then Ideas squashed all that.
I’m stopping there. Not gonna drag me in.
1 Like
Deleting draft responses, putting away gas can. Funny you mentioned Ideas squashed all that. I was just told by support since the program in question wasn’t work to use the Ideas Portal. I guess so we can vote for them to finish the program.
Well it can help prioritize finishing certain parts of the program before others. Actually, if people vote a certain way new features can take priority over bugs.
Patrick - If it’s anything like we do, I create the case to document the bug, give them steps to recreate in the edu environment, and then once EpiCare gets dev to accept the bug as a problem, I ignore it for the 2+ versions it takes them to fix and include into a release. Not much to do once it’s documented and done. And I’m hoping others are doing the same.
That being said, we should be getting a bug bounty! $ off maint, credits to Insights, or something. It’s a lot of work being un-paid beta testers!
4 Likes
Yes! Big bounty!
| askulte Andris Skulte
November 3 |
- | - |
Patrick - If it’s anything like we do, I create the case to document the bug, give them steps to recreate in the edu environment, and then once EpiCare gets dev to accept the bug as a problem, I ignore it for the 2+ versions it takes them to fix and include into a release. Not much to do once it’s documented and done. And I’m hoping others are doing the same.
That being said, we should be getting a bug bounty! $ off maint, credits to Insights, or something. It’s a lot of work being un-paid beta testers!
Are you still on 10.2.700.11?
The reason I ask is that the current patch level is .40 for 10.2.700 - and a lot of your issues were probably addressed in those patch updates.
If you’re upgrading to a newer version than that - I always advise people to not go up to the latest and greatest version of Epicor, as with every version, they break a lot of things ~ especially in the adhoc upgrade from client to kinetic interface. Alway upgrade to a mature version with many patch levels already released that fix all the bugs.
Edit:
(I’m not so lucky, as my current company is hosted on the SaaS cloud, and the longest we can postpone upgrades to is patch level .11 - and we’re always encountering issues with each and every upgrade).
1 Like
We’re on public cloud also…
| TDudek Timothy Dudek
November 16 |
- | - |
Are you still on 10.2.700.11?
The reason I ask is that the current patch level is .40 for 10.2.700 - and a lot of your issues were probably addressed in those patch updates.
If you’re going up to a newer version of that - I always advise people to not go up to the latest and greatest version of Epicor, as with every version, they break a lot of things ~ especially in the adhoc upgrade from client to kinetic interface. Alway upgrade to a mature version with many patch levels already released that fix all the bugs.
Edit:
(I’m not so lucky, as my current company is hosted on the SaaS cloud, and the longest we can postpone upgrades to is patch level .11 - and we’re always encountering issues with each and every upgrade).