the fact that the announcement closely coincided with a new look for EpicWeb (distraction?) is ominous…
It wasn’t a distraction the whole Epicor brand is changing and coming together into a cohesive look for their applications and sites
Kinetic is great and is getting better every day
1 Like
What I would like to know is, Has identity management within Epicor the hodgepodge collection of features and abilities and privileges and access and tracking been simplified and coalesced?
This is one area within Epicor which should be a source of embarrassment and resolved asap frankly.
“Identity, How I hate thee, Let me count the ways: User, employee, person, workforce, person contact, authorized user, buyer, inspector”…
How amazingly frustrating to introduce new people (people!) to Epicor and add them so they can do their work.
The other is the criticality of Lot when managing Inventory and selling in a Lot governed marketplace.
5 Likes
Just curious, will there be Epicor Insight this year for this?
I got my first support ticket concluding with “That will be fixed in 11.”
3 Likes
How long do you recon until on prem will have 11 ?
1 Like
Just started at a new company, they are doing a Salesforce integration- hooray!
Wait! We’re cloud and V11 is coming!
They are not going to stop this integration, regardless… So… Where’s the “this is how screwed you are” documentation???
Are there SF Epicor bridge geeks?
Thanks all, Y’all rock!
You are lucky to be getting answers, I have a few problems from 2018/19 that are still resolution TBD
-
A planning workbench bug - no check is done if the job number already exists when multiple jobs are submitted. Planning workbench will suggest a job to be created with the same order-line-rel number if the demand link is deleted. If a user tries to do this locally it’ll crash their client, if they submit to the server process it wreaks havoc on the database server. The jobs submitted to the process get stuck, and manual updating via SQL required to fix it. Submitted originally on 10.2.100, just yesterday got an update on the expected fix… 11.1.200.
-
Documentation states that configurator can create create a part record from the purchase order context - the checkbox in configurator entry is disabled though. Submitted on 10.2.200, only now finally got a problem for it. Date TBD. I tested too by manually enabling it via SQL on a test server and most of the functionality seems to work. Yet support says the documentation is in error and the feature was never supposed to be included. If the docs were in error they never removed it when I reported it on 10.2.200 because it’s still in the 10.2.700 techref last I checked.
-
Issue with receive time not displaying (or being calculated) on certain configured jobs, submitted in 2018 as well. Two PRB’s created against it. One that’s been sitting since 2018 with nothing done, another that got accepted the got rejected a couple days after getting accepted. So I’m still not sure what’s going on with it
-
I didn’t originally report this one, but the configurator code editor hanging when the “.” is typed. On my larger configurations it will hang for up to 3min, though intermittently. This is seriously annoying. It was originally reported in 2019, a PRB is in - no fix.
I have not been having a great experience with support at all.
2 Likes
Heh… we started getting that even before the announcement of 11.
1 Like
They’ve revamped some areas, but the issue for me is the disconnect between support and development. I have had a case open since August with no PRB number assigned (I’ve been assured it’s coming). Support wants to close the ticket without a resolution, so I’m stuck opening a weekly case to get a datafix. I’ve found when support can help, they do so. If they have to involve any other area of Epicor then things stop.
5 Likes
Communication is also a huge issue. ERPS get cancelled after support has closed the case (they are quick to do so without resolution) and I’m never notified.
My PRB flips from accepted to rejected, and though I do get an email. The link to find out my information is broken and I’m greeted with “Record not found”. My PRB is gone from the My Problems section too, and I need to open another case to find out what happened - which of course usually requires much back and forth.
3 Likes
This is an issue with the way they implement “intellisense.” The dll’s need to be downloaded from the server where they do reflection to get the signatures, and finally parse for the object the user started. I did code in VSCode and pasted it in and that doesn’t happen. If you’re in the cloud, wow, it’s a long wait.
1 Like
I was just told that this would be fixed in E11…
Aside, does anybody have configurator documentation for E11? I’m told they are changed significantly. We utilize configurations heavily. I’d love to see what’s upcoming so I can best prepare - and hopefully not have to rewrite completely.