11

I am fetching Unrecognized field: 'ntoreturn' error when i try to change page in my aws documentDB. I have used Robo3t for connect DocumentDB using SSH tunnel.

enter image description here

Ketan Modi
  • 1,780
  • 1
  • 16
  • 28
  • What tool are you using? Or how can I reproduce the error that you are posting? – Joseph Idziorek Aug 05 '19 at 01:22
  • 2
    @JosephIdziorek, i have used Robo3t for connect AWS documentDB – Ketan Modi Aug 05 '19 at 04:37
  • Can you please provide the steps to help me reproduce the error that you are seeing. I am able to connect and query my DocumentDB cluster from Robo3T but need your help on understanding what the 3 fields are and what query or action you took in Robo3T. – Joseph Idziorek Aug 11 '19 at 14:09
  • @JosephIdziorek, it's not about that 3 fields, in my collection I have lots of records. when I try to change my page it shows me this error. This error also shows after I delete any record. – Ketan Modi Aug 12 '19 at 07:25
  • @JosephIdziorek We're getting this error when trying to save an edited document. Appears that that edit did commit however. Worked just fine in previous RoboMongo client editions. Deleting a document also does it. – jmkgreen Aug 15 '19 at 15:59
  • 1
    @JosephIdziorek, I have used other GUI tools and it's working fine now. – Ketan Modi Aug 17 '19 at 05:08
  • @JosephIdziorek What tool did you end up using? I'm experiencing the same issue using Robo3T with DocumentDB. Results in being unable to page between results. – Skylar Graika Dec 01 '19 at 17:53
  • @SkylarGraika, happy to help, can you please help me repro the issues that you're seeing? – Joseph Idziorek Dec 01 '19 at 21:01
  • 1
    @SkylarGraika i have used nosqlbooster `https://nosqlbooster.com/` you can check this link. it is working quite well with documentDB – Ketan Modi Dec 09 '19 at 13:27

2 Answers2

6

Chiming in with Ketan Modi.

NoSQLBooster free version is an okay replacement for Robo 3T if not exactly a perfect solution. Had the exact same problem.

Jørgen Vik
  • 726
  • 1
  • 8
  • 27
1

In case somebody else has been having this issue, I had this same error message in version 1.3.1 but upgraded to version 1.4.3 and it appears as though it has been fixed.

zeiddev
  • 662
  • 7
  • 23