As a workaround, you may test it with CData MongoDB provider.
Creating a support ticket to follow-up on error details.
As discussed in the support ticket, the following error messages were present:
' error: unexpected SUB at position 245
' error: unexpected STRING at position 342 near gr_notifications
A bug fix (12567) was released in 20.10.26 to handle the issue of Incorrect Accent grave sign in General ODBC setup. The Accent Grave type was character ' this has been changed to `. ODBC connections using the Accent Grave are update to use the new Single Quote.
Using TX Classic (V20.10.61) - what’s the preferred way to connect to a MongoDB ?
I have an ODBC setup, and when I sync the objects, we get a list of tables and flattened tables (which are JSON’s in the MongoDB collection).
However, when previewing such tables I often get an error - saying that some columns don’t exist. Is there a specific ODBC driver we should use, or specific options we should set in the connection to make this work?
We figured out the solution to be :
- setup the MongoDB BI connector with fixed DRDL schema files
- setup the MongoDB ODBC connector (to connect to the BI connector)
This setup is easy to maintain ( DRDL files ) and is performing very well.