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

This thread is now closed to new comments.
Some of the links and information provided in this thread may no longer be available or relevant.
If you have a question please start a new post.
LiamSmith
Experienced Partner
72 Posts
Experienced Partner
Australia
Experienced Partner

72Posts

249Kudos

1Solutions

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"
2 REPLIES 2
Mike_James
Ultimate Partner
5,857 Posts
Ultimate Partner
New Zealand
Ultimate Partner

5,857Posts

1,026Kudos

756Solutions

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

Hi @LiamSmith , I've seen reference to this error where the file is v2019.4 and on the desktop. If that's the case here, please see https://apisupport.myob.com/hc/en-us/articles/360001359796-AR-2019-4-Local-API-500-InternalServer-Is...

 

The only solutions offerred are to upgrade to 2020.1 or put the file in the cloud. 


Regards, Mike (mike@datawise.co.nz)
DataWise Limited (www.datawise.co.nz), developers of:
DataWise ProActive - Custom Reporting from MYOB programs
(MYOB Business, including AccountRight Live, AccountRight v19.x and exo Payroll)

Bulk download of attachments (more details...)

LiamSmith
Experienced Partner
72 Posts
Experienced Partner
Australia
Experienced Partner

72Posts

249Kudos

1Solutions

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

Hi Mike,

 

Can confirm these are cloud files and pretty sure most are 2019.4.

 

The issue is we start seeing data from the API but then it stops mid way through when it hits 'bad' data inside the MYOB file.

 

We have an integration ourselves + also through another vendor and both have this exact same issue on the exact same files.

 

The only thing we've had back from the vendor was that they raised it with MYOB support, it's a known issue and to manually find the characters and remove.

The issue is they don't specify what characters or what's the easiest way to find them. 

 

Very frustrating!!

Didn't find your answer here?

Try using advanced search to find a post more easily Advanced Search
or
Get the conversation started and make a new post Start a Post