Skip to content

Atlas App Services

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

248 results found

  1. Adding or removing elements from array fields

    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.

    36 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)
  2. Ability to Reuse Types in Custom Resolver Schemas

    We are in the process of migrating from a hand-implemented Apollo server to Mongo Realm, but are finding the inability to reuse types on custom resolvers to be a serious impediment.

    For example, we have a number of custom resolvers that use the same type to define a temporal interval, but we cannot reuse that type in the arguments for our custom resolvers as Stitch will throw an error upon encountering those duplicated types. Additionally, many of these custom resolvers return the exact same type, but if we try to reuse that same type definition Stitch will throw errors about…

    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

    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)
    planned  ·  Drew responded

    Hi Folks – This improvement is already planned and should be completed shortly.

  3. MongoDB Realm vs Realm

    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

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Realm UI Ability Changes to Github Repo

    Please add git integration for functions and 3rdParty HTTP services.
    Everything I make a change to a function and it is deployed, Realm tells me what the changes are but they are not pushed to my own Git repository

    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

    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)
    Sumedha Mehta responded

    This was launched earlier last year -https://docs.mongodb.com/realm/manage-apps/deploy/automated/deploy-automatically-with-github/#make-changes-from-the-ui 

  5. Github Deploy

    When deploying from a Github commit, can you make the Realm files only update what is being committed? It seems like Realm is updating all files, which is taking forever when you have a bunch of functions, along with Hosting files, which in my case is a good bit.

    If I go directly into the UI and update a function from there, the Deploy happens fairly quick. But, as soon as I commit from Github, that function gets updated by what is in my Github Repo, which in this case, would overwrire what I just did in the UI.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Ability to query datalake / online archive

    The new online archive is awesome.

    What would be even better is if we could query the data it moves to S3 as part of our stitch/realm functions.

    Thanks

    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)
  7. Configure rate limit

    It would be nice to be able to configure rate-limiting to prevent DDoS, scraping or unwanted requests that could highly increase the cost of MongoDB Realms

    52 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. Disable Realm

    It would be great to be able to disable a realm without deleting it. Currently, this is possible by unlinking the cluster or exporting the realm and deleting it. Both of which create more work when firing it back up.

    It would also be amazing to be able to tie that in with billing alerts. Say I would rather my app crash than pay more than a certain amount because of Realm usage.

    In essence, I'm asking for an "always free" Realm that just disables itself when the free tier has been hit so that I can be 100% certain…

    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. 155 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)
  10. Support TypeScript

    I know this is probably a very complex feature, but I'd like to work with TypeScript when writing functions.
    Some stretch goals:
    - full integration with VSCode so we no longer have to use the web editor
    - add support for testing functions (through CI/CD)

    98 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

    8 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)
  11. on premise solution

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

    33 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)
  12. function sandbox

    It would be great to have a function sandbox area, where you can write and called previously used functions (saved like notepad++ does) without having to create the function and commit it.

    This would be for trying thing out or performing quick tasks for which you don't want to go through all the hassle of formally creating a function.

    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

    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)
  13. More descriptive errors

    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!

    9 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. 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.

    34 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)
  15. Dark Mode

    Support a "Dark Mode" for the MongoDB Realm UI.

    39 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)
  16. More flexible Custom User Data / User Linking

    On Stitch, you can have multiple providers for identity, but then it creates multiple users even with the same email address if you have someone from say Google or then someone who authenticated via email. There is a way to merge two accounts, but it requires the user to authenticate twice and that's not an ideal user experience. One solve is to treat them as one user. The other solve is to create a user metadata collection which both identities can reference, but if you're trying to add rules and permissions you can't put an array of options in the…

    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)
  17. Global Variables for Functions

    Add global variables to Functions (so I don't have to pass around supposedly global variables to every function call).

    Add support for typescript :)))

    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

    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)
  18. Allow deeper relationships under Rules

    I really like being able to use GraphQL and how you can auto generate a schema but when trying to relate fields I noticed it would only let me relate top level fields.

    For example - we have "accounts" and "users" under accounts with user Id on a related object. But I cannot do related userId back to account.user.userid since user is an object. I was hoping after I generated a schema for all the collection I would be able to drill down deeper but no such luck.

    20 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)
  19. Pagination in GraphQL

    We have slicing via limit: INT, but we do not have the ability to specify an offset. Are there plans to add this soon?
    GraphQL Documentation actually specifies their pagination terms as follows:
    first: int
    offset: int
    after: _id
    Are there plans to implement this at all?

    86 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)
  20. Inheritance / Polymorphism

    Support for polymorphism would be a huge plus. In particular, being able to define a class structure and then query for a base class (or interface?) to get a list of all the various concrete classes.

    Related GitHub Issue: https://github.com/realm/realm-java/issues/761

    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

    2 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)
  • Don't see your idea?

Feedback and Knowledge Base