-
Mirth Connect 3.8.1 on RHEL 7.9 Saw the following error information:
The cause was the lack of a comma after one of the properties in middle of the JSON doc. The culprit line, 2691, is the last line before the first Source Filter rule is run. Is there some way to capture that error, similar to the try...catch JS mechanism, in order to return a more appropriate response, such as a more detailed API response? Thanks in advance for your response. |
Beta Was this translation helpful? Give feedback.
Answered by
pacmano1
Oct 14, 2021
Replies: 1 comment
-
Yup, set the data type to raw on your inbound listener and |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
pacmano1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yup, set the data type to raw on your inbound listener and
JSON.parse
msg in a try..catch.