This might be useful and saves time and effort, if you encounter such error in Kinetic.
Lessons learned:
Prevent forbidden special characters in REST call for any string values used on User Interface.
@timshuwy
Epicor Idea:
You may cast your vote : Prevent/Replace Rest Forbidden Special characters while entering in any UI Text Box
Epicor should plan for sort of validation at text box control entry- Don’t let such characters to be entered
- If any special forbidden characters are entered, it should prevent user with specific error message.
- Or replace forbidden values with permissible equivalent values internally with control
- In the past we notice some instances with SQL too. If any special characters are passed from UI to database, Epicor gave generic error, hard to debug.
- We get this error message at SO Entry, adding new Release Line. As one of the text box in Calander table was using apostrophe in the text value called from Production Calander to stop user picking up declared holiday on order ship date. The root cause was the forbidden characters used in text values. However, Epicor error message was very generic, even the trace log won’t help.
- The other similar instance was also detailed on Yahoo group at: Kinetic 2022-2-5-not-making-any-rest-call-still-rest-exceptions-in-classic-form/97265. We had a support call, but our own deeper investigations, we notice same issues - use of forbidden characters in text box values. We had hyperlink using single quote in text string value. When we dropped out that with space, it starts working.