currently realm server which can use in Asia is too far and limited like below link
https://docs.mongodb.com/realm/admin/deployment-models-and-regions/#cloud-deployment-regions
so, i think it has some delay to request realm server as well as management using realm web UI
it would be nice to be able to use more close server

It would be nice to be able to managed Realm Applications via Terraform, similar to how MongoDB Atlas can currently be managed via the mongodb_atlas from Terraform provider.

"Int" is listed as a supported type for partition keys but it's not implemented. You should remove "Int" from the supported types since it's not supported.

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.

We would like to establish connection to OracleDB from a REAM Function. For that we're using oracledb npm module.

However this module is dependent on a third party binary (Oracle Instant Client “Basic” or “Basic Light” package), which should be in the PATH and located by the npm module.

Can REALM add support of this feature?

Ability to whitelist certain IP addresses for social media crawlers and send them to a function that does server-side rendering of the index.html page to create open graph protocol (https://ogp.me/) meta tags for a dynamic link preview depending on what the link is. This specifically applies for single-page webapps.

Should be able to link two or (preferably) more different email address credentials to 1 realm user.

Most obvious use case for this would be an app that has both a business domain, and a personal domain. The user can log in to their realm account with either their personal email addresses or their business email addresses.

Support client-side field-level encryption in MongoDB Realm.

https://docs.mongodb.com/manual/core/security-client-side-encryption/
https://docs.mongodb.com/manual/core/security-automatic-client-side-encryption/

Basically, it would be nice if we could mark fields as being "sensitive" in the schemas, and Realm Sync would make sure to encrypt the fields before they are sent from the client app to the MongoDB Atlas database.

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?

In the documentation for anonymous auth, it says that Realm may delete anonymous users that are 90 days old https://docs.mongodb.com/realm/authentication/anonymous/

There is also a mention about 30 days of inactivity https://developer.mongodb.com/community/forums/t/persisting-anonymous-users/10247/2?u=anton_p

That's hard to rely on something so broad to make decisions in the app logic. Is it possible to clarify this behavior or provide control over this flow?

The GraphQL feature has a history list while you stay on the page. It would be a great improvement if it maintained that history even if you navigated away and came back.

Users should be able to customize the reset password email that is sent to their users. This should include changing what the "sender" url looks like (noreply-stitch+mongodb.com => resetPassword@yourapp.com). Developers should have access to change look of the body of the email. This includes what is typed in the body, the title of the body and as well the company logo. I will upload a picture of how it currently looks and from my message understand what we want to change.

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 logs in a Realm app are viewable via the UI or via the API.
The API limits return results to a maximum at 100 a time.
I would like to be able to save logs (errors, especially) into a collection so that I can query or analyze them how I see fit.

The current work-around is ensuring that each of my functions has an appropriate try/catch/log, effectively replicating the logging Realm already does. Put another way, please expose the logs in a way that we can truly query them.

Realm Studio is helpful to explore data from Legacy Realm Cloud. But Realm Studio mongodb does not support opening 'Realm Cloud'.
Please consider this feature.
Thanks so much,

Use views (not materialized) as source for realm sync (potentially as read only)