At this time, the only permission that allows access to Realm is Project Owner; however, Project Owner grants permission to change a plethora of things inside Realm. In our case, we have testers who do not need the ability to change code. The testers only need to change Values and add users. Could a new permission class be created to support this?

It would be helpful to support array add/remove in update mutations. I've been running into this most often when dealing with one-to-many relationships.

For example, adding/removing books from an author. Currently, you would have to fetch the entire array of books to add or remove the book linked to the author. If I could supply the foreign key to add/remove from the relationship that would be fantastic.

Please add support for cascading deletes.

Related GitHub Issues:
https://github.com/realm/realm-core/issues/746
https://github.com/realm/realm-java/issues/1104
https://github.com/realm/realm-cocoa/issues/1186

Allow MongoDB to be used for on-premise solutions to offer early on integration or govcloud support for Realm.

As far as I understand currently it is not possible to use node/npm modules is Functions. Would be great to have it.

A lot of 3rd party libraries don't work, even ubiquitous ones like Joi. We upload zipped node_modules and all we get are errors.

Devs now spend time building simplified versions of these libraries so we don't get the full benefit of a using a battle-tested library and also waste time writing functions that we shouldn't need to write. This is a huge pain and a productivity killer.

Currently it is only possible to link a Github account for deployment.
It would be great if we can use Bitbucket as well. I have my code in a private bitbucket repository and would love to have the ability to deploy from it.

Dear MongoDb GraphQl Stitch developers,

Is it possible to add an ability to modify the final GraphQl schema (in order to remove unnecessary for my API stuff)
OR
Build it based on existed roles?

For example, Im building a "read only" GraphQl API and have NO roles that can actually modify the data. So I find it illogically to have mutations in the Final GraphQl schema.

It would be great to have an ability to choose which exactly mutations/queries I need for my GraphQl.

Thank you.

Option to export all Realm app users and import them.

It's a major concern that users can't be exported. Both for backup reasons and also for moving them between apps.

If you delete or loose a Realm app you are out of business because the users are gone and if you mistakenly chose the wrong deployment region, you can't move the app because you can't move the users.

I think this is absolutely critical to growing a business using Realm apps.

Add REST Services support analogous the GraphQL.
Some users on Realm desire a REST API to their clients as
oppose to a GraphQL API.

Although this can somewhat be accomplished by adding a HTTP '3rd Party Service' and query the mongo collections, you don't get all Rules, Schema, and other useful tools and services which are provided with the GraphQL option.

There seems to be no documentation how to write good tests for realm at this moment.

Support for Vue / Nuxt

Would be great if we can have more options for realm like south america and europe.

In the users tab, I can only search by ID. If I don't have the users ID, it's nearly impossible for me to find a user in the list. Need to be able to search for a user by email ASAP. Thanks.

A flag to enable/disable cloud sync on Fully-synchronized realms.

This would be convenient if you're offering sync as a premium feature.

Hi, I am an existing Realm/Realm Cloud user and am struggling to understand what the MongoDB Realm offering is and how it compares with the existing Realm/Realm Cloud solution.

Is there any documentation that explains what the difference is between the two solutions and what if any migration is required.

It's not clear whether the latest cocoa Realm database v5.1.0 is still compatible with Realm Cloud nor is it clear whether there is any plan to continue supporting the current Realm Cloud solution. A nice clear description would be much appreciated.

Regards
Duncan

We need more error codes for different situations. For example, using the wrong details while logging in returns 46 (Unknown), with a message indicating wrong credentials. In my app, 46 maps to a message like "An unknown error occurred. Please try again later.".

It would be nice if wrong credentials had its own error type so I could send a more descriptive message.

Please also consider this for any other error type that doesn't have a good reason for being Unknown.

Thanks!

As requested in this Github issue: https://github.com/realm/realm-cocoa/issues/5334

This item is also called out within the current public roadmap: https://www.mongodb.com/realm#roadmap

Provide complete, end to end support for macOS in MongoDB Realm. It will bring enterprise level capability to the desktop and allow total integration across (Apple) devices. Imagine a large factory where the workers can use their iPhones track or report work progress and then management being able to review those reports on their desktop.