Invalid/restricted characters in transaction descriptions causing API call to fail

Hi Team,

 

We have a number of ledgers (5 out of 400) where the client is using either import functions in MYOB or other addon's to push data into MYOB.

 

The issue seems to be that you can import/create via add on a description on a transaction which contains invalid/restricted characters without any issues but that the JournalTransaction API endpoint will then choke and error on when trying to read them back.

 

Can you please give me a list of characters that this occurs with so at a minimum I can go back into the GL reports and find/replace those characters so the API will work correctly?

 

Ideally; fix it so the API doesn't choke!

 

Cheers,

Liam

 

1. {title: "An unhandled exception occurred", status: 500,…}
   1. detail: "Encountered a communication error (https://ar1.api.myob.com/accountright/<REDACT>/GeneralLedger/JournalTransaction/?$top=400&$skip=0&$filter=DateOccurred ge datetime'2019-07-01' and DateOccurred le datetime'2020-06-30')"
   2. instance: "urn:<REDACT>:internalservererror:<REDACT>"
   3. status: 500
   4. title: "An unhandled exception occurred"