2025.2.6 Mass Receipt issue

:face_with_peeking_eye:

Dare i say another issue with 2025.2.6? So there is an issue with Mss Receipts in that when you book in lines of different types it messes with the Lot Numbers and then overwrites them with a new one, like wtf. I raised a ticket with support and it was a known issue which isnt fixed until 2025.2.12 which i know has just come out but i am no looking to upgrade again when i only just upgraded to .6 last week believing it was reasonably stable.

I have asked for a retro-fix for .6 but that needs to be approved, so if any of my EPICOR friends are lurking, please have a kind word :+1:

3 Likes

We are on 2025.2.10 and are having the same issue.

Support has said it is a known issue and is fixed in 2025.2.12, i have asked for a retrofix for .6 as i am not planning on updating just yet after recently updating.

We are on 2025.2.10 and are having issues with Lot Generation popping up something, even when we don’t use Mass Receipts. @jgiese.wci is tracking that one.

2 Likes

Are you saying that a patch update introduced a mass receipt error for you?

Yep, upgraded to 2025.2.6

1 Like

From what though? 2025.2.4?

2024.2.11

So not just a patch though, that’s a version change, up through a release.

That makes sense. I just wanted to give some context to the change for anyone else reading.

Sorry you are dealing with this.

No worries, not sure what the others have done?

What others have done about what?

Some other users are seeing the same issue, see further up the thread. Both of those are on 2025.2.10, whether they just performed a simple patch update and are now seeing the issue :thinking:

1 Like

I see what you’re getting at.

There’s this age-old saying that “you don’t need to test patch updates” and I was trying to see if it was a simple patch update that introduced this or not. Maybe in @hkeric.wci 's case it was, you’re right.

1 Like

So i have just received the following back from support with regards to my retrofix request -

So upon chasing this and speaking to dev support. i asked if the .12 fix is compatible with .6 but unfortunately this is a Knetic UX change and it cannot be moved back to .6
So it only leaves us with one option, that will be to take the latest update 2025.2.12 where the issue has fixed.
Apologies but this will be the only way to fix this issue.

Does that sound plausible?

1 Like

Sadly yes, sounds like you’ll need to upgrade to .12

We are experiencing the bug in Receipt Entry Classic.

2 Likes

I am not keen on having to upgrade to .12, there could be untold amount of issues that i am not aware of. :rofl:

1 Like

Understood, we’ve been burned before too.