Get Inspire insights from former attendees in our AMA discussion thread on Inspire Buzz. ACEs and other community members are on call all week to answer!

Alteryx Server Discussions

Find answers, ask questions, and share expertise about Alteryx Server.

Alteryx Server Mongo Connection No Longer Working

ryan_pip
6 - Meteoroid

I did the upgrade to Alteryx 2018.1 on our scheduler on friday.  Most of our processes have moved across fine but the process that pulls our logs from the MongoDB has started throwing an error.

 

The Macro I used is based on 

https://gallery.alteryx.com/#!app/Alteryx-Server-Scheduler-Status/5786057ca248970b4462ef8b

Which has been modified using filter similar to this

https://community.alteryx.com/t5/Data-Sources/Date-Filter-in-Mongo-Input/td-p/92957

 

It currently uses this filter that then has the id dynamically changed on runtime:

{_id:{$gt:ObjectId("5685c1800000000000000000")}}

I am getting this error:

Error: MongoDB Input (3): Got parse error at "_", position 1: "SPECIAL_EXPECTED": could not parse JSON document

 

I also tried:

{"_id":{"$gt":ObjectId('5685c1800000000000000000')}}

--> Error: MongoDB Input (3): Got parse error at "O", position 14: "SPECIAL_EXPECTED": could not parse JSON document

 

Anyone have any ideas?

 

Workflow is attached

 

1 REPLY 1
bginberg
5 - Atom

We had the same issue when we upgraded. Worked through it with Alteryx and discovered some info about MongoDB Extended JSON.

 

Here is a link to the syntax that worked for us: https://docs.mongodb.com/manual/reference/mongodb-extended-json/

 

I'm not sure if this query will work for what you are trying to accomplish, but I replaced the objectid with the formatting of the extended JSON below (similar to the change I made on my end) let me know if the below works for you - otherwise you will likely find what you need in the link above.

{"_id":{"$gt": {"$oid":"'5685c1800000000000000000'}}}

 

Hope this helps!