QueryParserError: Invalid content. Lexical error

If you get a failure creating a record in QuickBooks with an error like:

QueryParserError: Invalid content. Lexical error at line 1, column 59. Encountered: "\u2013" (8211) after "Example "

If there's enough information in the error to identify the field that's causing the error, then edit that field in ConnectWise Manage, and re-type the data in that field.  It's very important that you retype it, do not copy and paste.  (the invalid character that's causing the error probably got into Manage in the first place by copy and paste).

More detail:

This error is caused by a unicode character in your data that isn't accepted by the QB API.  In this example we have a company named "Example – Company".  The dash character in this company name is not the same as the minus sign you would type with your keyboard (Unicode: U+002D), instead it's the En dash character (Unicode: U+2013).  This would be similar to copying an emoji character into the company name.  QuickBooks isn't set up to handle these characters, so they must be removed from the data we send to QuickBooks.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.