Hello all. I had a data directive in place that would fire on InvcDtl whenever a row was added and check for RMANum > 0. When that happened, I would programmatically add a Misc Charge to that InvcDtl using the BO ARInvoice and following the logic seen when tracing the application. This was working OK until the 2026.1 update. I am scratching my head because it crashes now when I try to add an RMA Credit. I went through and tried several other workarounds such as using an UpdateExt to add the Misc Charge and the other UpdateMasters available on ARInvoice. Finally, I tried switching to a method directive and firing on RMAProc.RMACreditAdd (instead of data directive on InvcDtl). This is frustrating because I am getting an error that says there is a compilation error when trying to enable the BPM even though the syntax check and validate directive both return without any issues. I get this error even when I just put a Show Message widget on the BPM to confirm that it’s working.
Any ideas why this might be happening and/or a better method for automatically adding a restocking fee (misc charge) to a credit memo request generated from an RMA? There’s probably something so much simpler and I know someone out there has the magic wand.
2026.100 moved up to EF Core which is more restrictive plus they disabled MARS. Since this is when it broke I naturally think EF Core/MARS issue but could be something else. What errors are you getting in our BPM? That may help diagnose what’s going on.
It’s the generic error that says to contact support with a code. I have yet to follow through on that because it’s crazy that I can’t just look at the logs… but I may have to if I want to get this working.
But I like your thought about the function. I heard all about the EF Core but I guess I missed the MARS thing. What’s MARS?
That actually might be my issue. It’s trying to create an RMA Credit from the RMA screen which then creates a Credit Memo which it then launches… In the middle of that I’m adding a Misc Charge. I bet that’s my problem.
You need to get the server logs and find the Correlation ID to get the real error. It’s totally annoying and IMHO totally unnecessary but it’s the way Epicor did it and won’t change it.
You can use @GabeFranco’s EpiDev to search the logs without having to download them. It’s been a godsend for that plus for finding and fixed MARS issues.
I have read a lot of his posts and user commentary about it. I am super interested in trying it. But, alas, it’s over my head. I tried to set it up on VS and I can’t get past the initial logging in… lol. I thought I read that it was free to use the read only… but I can’t even figure out where to go to pay for it… ugh I feel old.