2022.2.5-Not making any REST call, still Rest Exceptions in classic form

We had a heavily customized form in C# which was working perfectly well in 10.2.500.28 and also no fixes all errors at uplifting to Kinetic 2022.2.5. As it’s heavily customized we will plan to have kinetic UI later. We noticed this strange error only with one record. It’s happening at update/save record.
I am believing with from past experience that if any sql field contains special character, this will throw error and failed save/update events. But in Kinetic, we get this strange error, even though we are not using kinetic forms or any rest call.

Let me know, if more details are needed.

Anybody notices this type of error in kinetic with classic forms. Any thoughts will be appreciated.
Thanks in advance for your time to read.

With more investigations, I noticed that with kinetic upgrade the same BPM working before now erroring out. the root cause was the file path string 'S:\Production\VEE Manual Instruction Files\Crypto IP ECN\Instructions’. When I get rid of : single quotes and backslashes and replaced with spaces- all worked as expected.

Lesson Learned:

The same file path was working well in 10.2.500.28, Which now causing strange error message that was hard to trace. I assume now in kinetic, BPM are using internal rest call and break down with sql update when - it contains listed special characters.

It take lot trouble shooting to figure out the root cause. It would be better if Epicor error message says more context related message.

1 Like

You assume correct, but widen your scope. The entire classic interface now uses rest on the backend.

Using Epicor’s Ice Framework shouldn’t have this problem. Are you doing direct database updates? For Epicor workloads, it’s not recommended.

Also, updates should happen at the server and not from UI customizations.

Not at all. We never had any direct sql update and aware with consequences. All works well in previous version, nor with Kinetic it breaks. looking at the error, and with past experience, if we any special characters not visible, but it may create issues with save/update the record.
Per @klincecum - Thanks, now all classics UI forms, internally making rest call to the server. That explains the REST don’t let us to sue forbidden special characters.