This was working in 2025.1 but now (2025.2) AP Invoice Job Misc Mtl Lines do not show up on T&M Invoice Review.
Is anyone using this on 2025.2 and can confirm it isn’t broken. We’ve checked everything we can think of and cannot find any issues.
I’d rather downgrade Pilot than open a Epicare case.
UPDATE:
Thanks for your reply @timshuwy . You’re right we need to report issues. I just wish it wasn’t so painful or at least there was a sign the support experience might improve.
I’ve created the case and will document the progress here.
If it goes the way most do, this will be the last time I put in the effort to document the experience. If it goes better than expected, Bravo!. I’ll be the first to admitt I’m wrong.
Prediction based on experience: The next thing to happen is they’ll want exact steps to repeat the issue in EDU. I’ve already given pretty clear outline, mind you, anyone with a tad experience (i have very little we’re not even live yet) would be able to fillin the blanks. I ELI5 it for them and then they ask to do a screen share. It’s been days now cuz they were trying things and I was typing, etc. We’re both losing money fast at this point, but we’re not even started. I don’t have time for a screen share, they have what they need to repeat the problem, I’m trying to go-live in a month but I do it anyway.
On the call, I’m queueing up to get this over with and the technician asks if I can do it in the old client cuz he doesn’t have kinetic.
well i dont have the old so you’re shit outtah luck I say n ask for someone else…it goes down hill from there.
A few days later he’s still struggling to repeat the prob I guess so I record a video after hours and upload to the case. After a few escalations because I dont hear anything for a week or more - he claims to have repeated the problem (doubtful) and submitted to dev. It sits in planning to plan to plan status or whatever forever and that’s that.
Woah, you actually have support asking you to run in classic instead of kinetic ‘because they don’t have access to kinetic’?
I’m not Epicare’s biggest supporter but I will say it has been a while since I even got the ‘use classic instead of kinetic’ as a work around so it surprises me that anyone at support wouldn’t be kinetic first at this point.
To be fair, this experience was months ago and the ask may’ve been ‘would it be possible because i’m more familiar’ rather than ‘don’t have access’ but still a true story and off-putting nonetheless for a new customer whos never even seen anything other than kinetic.
If you (or ANYONE) ever gets a reponse like this, you have my permission (and the permission of the support leadership) to ask for an escalation to someone who can help using the browser. It is not an acceptable option to go back to the smart client, UNLESS you are doing some form of comparison between the old and the new.
Also, I have found that to submit a ticket that is complicated, sometimes it is just easier to create a demonstration video using a tool such as "ClipChamp by microsoft. This is the tool i use to record all the feature spotlights, and it is super easy. Then you submit the video with a short text description. At that point, they can simply send it onto development. (Less friction = faster response).
EOB Day1. Very first update from support was (to effect) “after extensive testing I was able to recreate the problem, have provided to dev, and will keep you updated”
Bravo! So far so good. I stand corrected.
Remember, that light at the end of the tunnel could just as easily be an oncoming train…
EOB Day 2: Development Task TASK746xxxx added to support this case
EOB Day3: nothing
AM Day4:
2025-11-21 08:21:08 -Development Notes
Development Task TASK7463549 had notes added:
Problem PRB0308293 have been updated:
PD State have been updated to: Accepted - Not Yet Planned
Which is it 2026 or 2024? Either way we’re out of luck on 2025.2.x (?) We’re trying to go-live and functionality we need is reverting… what a mess.
Day4 again:
2025-11-21 08:56:08 -Development Notes
Development Task TASK7463549 had notes added:
Problem PRB0308293 have been updated:
Fixed in Release have been updated to: 2026.1, 12.1.100, 2024.2.13
2025-11-21 08:51:11 -Development Notes
Development Task TASK7463549 had notes added:
Problem PRB0308293 have been updated:
PD State have been updated to: In Release Planning
Fixed in Release have been updated to: 12.2.100
2025-11-21 08:51:08 -Development Notes
Development Task TASK7463549 had notes added:
Problem PRB0308293 have been updated:
Fixed in Release have been updated to: 2026.1, 12.1.100, 2024.2.13
Honestly, I don’t even accept trying to compare to any smart client .dll’s due to the fact they stopped incorporating new functionality into the smart client forms quite some time ago; and thus are pointless when trying to compare to the browser UX.
Since Kinetic, support has drastically deteriorated. I’ve had to escalate Edge Agent printing issues twice already, and the most recent wants a copy of my database, when the issue is clearly edge agent communication between the browser and printer - sometimes it works, other times it immediately throws up a print preview. It’s been a month since I opened the support case, and the original support response was that edge agent isn’t needed for On-Prem because we have the smart client (in which I haven’t deployed at all).
Support is a cluster, right now.
Didn’t mean to go off-topic, but it is what it is. It’s starting to feel like support really doesn’t care about any of us or our issues; nor whether they get resolved or not outside of being something they can pass off to the development team to be fixed at some mystical future date and time.
Day 14:
Our Development team has provided the following details:
Target Version: 2025.2.12
Release Date: February 4, 2026
Nice that’s our go-live date. delaying yet again.
PSA - if you rely on this feature you may want to flex 2025.2.7 before next week if not already too late
Day 16:
Development Task TASK7463549 had notes added:
Problem PRB0308293 have been updated:
Fixed in Release have been updated to: 2026.1, 12.1.100, 2024.2.13
I’m on 2025.2.7 = 12.1.100.7 but whatever.