It's here.... 2026.1.100 Feedback Thread (Behave 🤣 )

Rest API Help still works for me. So, its not an across the board issue.

Sounds like its related to the recurring redirect issues with the rest help page. Are you using idp?

Wasn’t there a Duplicate Function feature in classic Function Maintenace? Cannot find it in Kinetic Functions Studio.

Its right here:

I am indeedy using idp

Sounds like a support ticket.

indeed, thanks. > gets more coffee.

do we have a PRB for this? im IdP and experiencing the same.

Just stumbled by accident into the ā€œEpicor Kinetic Updatesā€ button

image

Where’s that?

Any date selector.

I am not seeing it

Ah, sorry I see it now! :grinning_face_with_smiling_eyes:

We’re still trying to get EDI/filepath stuff straightened out…some stuff’s OK, others not so much.

Just noticed something odd on Customer Shipment Entry - looks like it’s showing packs from ALL FOUR of our sites/plants…and not just limited to the one I’m in (as it is in our Live environment).

EDIT - CS0005508591

Good afternoon,

Just wondering if anyone has experienced anything like the situation mentioned below in the new Pilot 2026.100.5?? We cannot get our EDI to import correctly.

We are using Demand Entry to Import .app files into Epicor. There are 3 user hooks in the Method Directives that appear not to be firing any longer since the upgrade. They are: Erp.BO.DemandImportEntry.ImportEDIb4Val, Erp.BO.DemandImportEntry.ImportEDIPostProcessDemand and Erp.BO.DemandImportEntry.ImportEDIPreProcessDemand. Did these get replaced in 2026.100.5??? Is there any reason why they would not be firing??

Please let me know if anyone can help. I did submit a support ticket but thought I would try here also.

Thanks!

Filepaths change in Linux/Pilot, so the ā€œImport EDI Processā€ pulls from a different folder.

In Windows/Live - take out the parens around the . - XXXXXX is your Epicor customer ID: \\XXXXXX.file.core.windows(.)net\XXXXXX\Live\EDI\In\

In Linux/Pilot: /epi/fs/Pilot/EDI/In/

John,

Thank you but I am already past that part. Had all my notes from earlier this year during the Linux fiasco.
The files get imported into Epicor Demand Entry but the Method Directives that are User Hooks that I mentioned do not fire to have the files import 100% correctly. Any idea about that??

OK, we’re in the same boat then…orders came in but not 100% right as BPMs aren’t firing. Our consulting company is investigating. We just did a Live-to-Pilot the week before the upgrade too…so some of our issues could be tied more to that than 2026.100. Good thing we’ve got a month to test. :slight_smile:

@JMPCONJ and @JillMetalworks those 4 methods have been in the EDI documentation since the beginning, hopefully they weren’t removed. Watching closely, let us know what you find :eyes:

LOL…that would be very problematic. Our orders are getting in - they’re just not firing off some date related BPM logic. Also seeing errors in SO Entry itself…BPMs also not firing. There’s probably a library missing or something wasn’t enabled or some other such mess.

And to top THAT off, our Live EDIHQ is hung up right now too.

It’s been a grand day.