Raising Purchase Order Errors since upgrading to 2024.2.9

Hello,

Has anyone else recently updated to 2024.2.9 and facing unhelpful errors when trying to raise a PO?

Just manually trying to create a PO, then upon saving I get this error, I don’t see anything remotely helpful in the developer tools either.

image

Running dev tools:

There was a data directive we had enabled which auto-approved PO’s which has since been disabled but the error continues.

We’ve also tried resetting the customisation layer to base layer and raising a PO from there.

Thanks in advance for any advice! :slight_smile:

Did you already check if it fails in classic too? Are there any method directives?

1 Like

Thank you Alisa, I just tried Classic version and this gave me much more information!

It was an error in relation to the Extension Schema Serialize needed running which has now resolved that error but keep getting a different error in replace of it when logging in / trying to create a PO.

image

Can you please vote for my idea to bring error messages back to Kinetic? This type of thing is a perfect example of why kinetic is becoming so useless. Back to your error though, did you check conversion workbench after your upgrade to make sure none of the conversions failed?

https://epicor.ideas.aha.io/ideas/KIN-I-5938

5 Likes

Aw sorry Alisa, I don’t have an account with Epicor as we use 3rd party otherwise I’d vote it up for you. Is there an alternative way I can do it without needing a log in?

Thanks for the data conversion suggestion, managed to clear those errors by running another regen of the database, and now it’s circled back to the original error below.

I think I need to install the 2024.2/11.3.200 UK CSF but I can’t find an install for it on EpicWeb… :thinking:

So either your csf was not installed correctly, or not at all after your upgrade. Notice the version 11.2.100.0 Based on your profile you are 2024.2 which translates to 11.3.200.

I checked Epicweb, but we don’t have a UK CSF licence, so I don’t see it there.

So if you can’t see it you’ll need to contact support.

1 Like

Perfect, thanks for confirming!! :smiley: I’ll raise it with our support contact.

1 Like

Please mark as solution if it is :slight_smile:

1 Like

Let us know how you get on.

I’ve now got a copy of the CSF file and updated it, its resolved the issue for us. Thanks :smiley:

1 Like

Yeah! It’s the small wins… Glad I was able to help

1 Like