Skip to content

Atlas App Services

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

262 results found

  1. Automatically Refresh Auth Tokens on User's Custom Data Change

    Currently, getting updates to custom user data on the frontend requires periodically refreshing the token. A potential improvement would be for MongoDB Realm/SDKs to detect these changes automatically and streamline the token refresh so application code wasn't required to handle this case.

    35 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Passwordless authentication provider

    Passwordless logins are quite commons nowadays. Firebase supports "Login with email link" (https://firebase.google.com/docs/auth/web/email-link-auth). Would be nice to have the same in Realm.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Custom Query Filters

    While you can create custom resolvers for 3rd party data or functions, this doesnt help me use graphQL to search existing types. I want to be able to query an existing type based on a contains. I know that this is a complex issue, but if we could create a custom query filter like we do for in, gt, lt, etc, I think this would help make the graphQL API more usable.

    Currently, we are reduced to either using the limited query abilities, or recreate everything from scratch.

    For instance:

    I have a query currently:

    query {
    authorizationGroup(query: { name:

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  GraphQL API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Allow one-to-many relationships in Realm GraphQL

    Two collections A & B. One field say _id of collection A is the "foreign key" for a field say "field1" in collection B.

    A: {_id:1, k1:v1, k2:v2}

    B: {f1:1, x1:y1} //Values of field f1 correspond to values of _id in A
    B: {f1:1, x1:y2}

    For one value of _id in A, there can be multiple corresponding documents in B. If we create a relationship currently in Realm GraphQL, only one document is fetched. The expected result set is 2 documents.

    The current cumbersome workaround is to add an array field in collection A with all corresponding document IDs from…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  GraphQL API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Search Users by Email

    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.

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Add More Regions For Realm

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

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Increase max 100 item limit from Realm Logs API

    Currently the API has a hard limit of returning 100 results. For any sort of real diagnostics with the logs, this is pretty much worthless -- with a large quantity of transactions, the only thing I can think of to do would be to write a script to loop through time intervals and aggregate them on my side.

    As a real-world scenario, I was trying to identify the full scope of impact of a bug that went out and was not caught for a couple days and ran into the limit. It was also difficult to even identify exactly when…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Realm update/replace logs

    I think an enhancement to the realm logs that explains the deltas (what has changed) on a given document for updates/replace would be extremely useful.

    At the moment we receive an ID and the type of change that has happened which is fine for an insert/delete.

    But to understand what has changed on the document for an update/replace would help a lot in diagnosing any issues we have seen with realm in the past.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Allow editing of the generated GraphQL schema and resolver

    The data model that I want to expose to the user is not the one that I have in MongoDB, having this feature would be nice

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  GraphQL API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Injection Attack Documentation

    Hi MongoDB, we are in the process of preparing for production and while we have found some susceptibilities to injection attacks on mongodb (see OWASP Top 10) there does not seem to be any documentation explaining all the potential known avenues of attack for MongoDB. The response from the engineering team is there is shared responsibility, however, how can we share responsibility for what we do not know? We as engineers rely on the product owners to give known attack vectors so that we can share that responsibility.

    That said, there are two we know about, escape for the $…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Support of multiple partition keys

    You could actually increase the awesomeness of MongoRealm, when you support multiple partition keys on one object.

    Example:
    We have a collection of customers in MongoDB, our App is showing the customer information to the users, but only for those users, that are "allowed" to see the customers. So the customer object has a partition key holding the userName it is assigned to:

    customer { _id: "12345", partition: "bob", name: "MongoDB Inc."}
    customer { _id: "12346", partition: "alice", name: "Microsoft"}

    now we want, that alice also sees the customer "MongoDB Inc." in the App.

    The solution could look something like…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Device Sync  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Single schema of truth: JSON Schema / Realm Schema / GraphQL Schema / TypeScript Types

    I think the current recommended initial prototyping workflow for a Realm web SDK user is like this:

    1) Add first data in collection (manually, on Compass etc.)
    2) Generate JSON Schema (manually click a button on web UI)
    3) Set up relationship (manually, on web UI)
    4) Download GraphQL Schema (manually click a button on web UI)
    5) Get TypeScript types and React hooks (automatically generated by graphql-codegen CLI)
    6) If you use another Realm SDK somewhere else (ex. Node.js sdk for server side), write Realm Schema (manually)

    This is not very developer friendly, and requires back-and-forth work between CLI,…

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  GraphQL API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Add Google Cloud as 3rd Party Service

    Please add Google Cloud as 3rd Party Service.

    I tried upload as a dependency but when running my function it complained about missing http2 module.

    Tried installing http2 as dependency but then hit into another error: "
    Cannot access member 'HTTP2HEADERSTATUS' of undefined"

    By the time I think it won't be possible to do that, unless Google Cloud is supported by MongoDb natively.

    The package I was trying is:
    const vision = require('@google-cloud/vision')

    Thanks!

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. External Dependencies Should Be Per Function

    10mb compressed size constraint is very limited. Plus, dependencies are not siloed per function. Either uncap the dependencies constraint or allow dependencies to be uploaded per function, still with a higher compressed size constraint (preferably at least 100mb to support large dependencies such as for image processing).

    I think the thought was "functions are meant to be short running operations" but I think that is a huge assumption. Why not offer options for powerful compute that respond to database change events. Sure you may need to just update something else in the db, and that may be sufficient for some…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Functions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Programmatic Support for Uploading Dependencies

    Right now the Realm Administration APIs [1] only let's users list dependencies. It would be helpful to have an endpoint to upload dependencies as we have 8 env and uploading manually to all envs is painful.

    [1] https://docs.mongodb.com/realm/admin/api/v3/#dependency-apis

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Schema for Realm's JSON Files to Enable Auto-Completion

    This is a minor suggestion but it will be great if intellisense works for Realm-specific json files (i.e. "auth_providers/api-key.json", "services/mongodb-atlas/rules/db.collection.json", etc).

    It will be helpful for developers using the Ream's "Deploy with CLI/GitHub" feature (which is great). I guess it may help reduce confusions; for example ObjectId/ObjectID/objectId.

    VSCode has built-in support for JSON schema, and it seems additional schemas can be specified via three options: $schema in the file, VSCode settings or an extension.
    https://code.visualstudio.com/Docs/languages/json#_json-schemas-and-settings

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Migrate Firebase Cloud Message from legacy HTTP to HTTP v1

    I am very happy with Push Notifications using FCM but currently, FCM has been update to HTTP v1 and I saw that MongoDB Push Notification still using the HTTP. With HTTP, I can't send an image in the notification payload (https://firebase.google.com/docs/cloud-messaging/android/send-image), also the data payload is different when I send message directly from FCM.

    I hope that MongoDB have plan to migrate Firebase Cloud Message from legacy HTTP to HTTP v1 (https://firebase.google.com/docs/cloud-messaging/migrate-v1)

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Actual API Documentation

    There is various documentation for the many Realm/Stitch SDKs but almost no information about the underlying API endpoints, this needs to change and we need some detailed docs for working with the API itself.

    I am trying to get an app running with the GraphQL API but have found working with the authentication APIs to handle auth tokens and sessions to be a bit of a nightmare. This page https://docs.mongodb.com/realm/graphql/authenticate/ has some useful information but doesn't even give the endpoints for logging out or explain how to properly handle the email sign up process using API endpoints in place of…

    18 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Selective Realm Reset

    We are running Realm Sync from an iOS app (RealmSwift 10.7.2). We have a problem where the data related to one Realm partition is giving is a BAD CHANGESET error in production due to a data
    issue. My suggestion is, can we cancel Realm Sync operations for a particular partition as opposed to terminating the sync for the entire app (all partitions) which would force all of our users to reinstall their apps so a fresh local copy of the Realmfile is built)? We don't want to be resetting across all partitions because it impacts all production users and in…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Device Sync  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Ability to change/update email address of Application User

    Users should have the ability to change their email address.
    Applications cannot give the ability to users to change their own email address. Once a user is registered/created there is no way for such user to update/change their own email address.

    56 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 2 6 8 10 13 14
  • Don't see your idea?

Feedback and Knowledge Base