Skip to content

Atlas App Services

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

91 results found

  1. Re-Add support for querying LinkingObjects with GraphQL

    In RealmSwift, one can define LinkingObjects to refer to inverse M2O or M2M relationships. These are not supported by queries in MongoDB requiring to create custom resolvers. It would be very useful if these would be accessible in GraphQL.

    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)
  2. Set custom endpoint for s3 service

    Allow users to use a custom s3 endpoint for example: nyc3.digitaloceanspaces.com

    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)
  3. Expose default confirmFn for use within custom confirmFn

    In my application I have implemented a custom confirm function which blocks registrations unless they have an email address in my company's domain. When this is the case, I would like to send the signup email as usual. However there isn't a way of doing this so in order to implement this basic filter I have to setup a 3rd party email service.

    It would be good to allow calling the default confirmFn from within the custom one

    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)
  4. Github Authentication Provider

    Right now there is Google, Facebook, and Apple as auth providers. Would like to see Github added as well.

    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)
  5. More Intuitive GUI for Relationship Modeling

    I know "Add Relationship" button works very well. However, you can check some of Headless CMS out there and learn from how they are letting users to handle relationship modeling.

    I think the one from Strapi is the best. It's like attached image.
    You can search on google image by "Strapi relation" and find more images.

    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)
  6. Improve Realm Web RBAC Granularity

    Currently, You need to be a "Project Owner" to view GraphQL configurations in Realm Web. I also need "Project Owner" to execute a schema validation. I would like to see more granular access controls for Realm Web similar to the granularity of MongoDB Atlas.

    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)
  7. Custom OAuth 2 Providers

    Allow us to input custom oauth2 providers for login. I know we can do something similar through custom functions, however, it would be nice if we can just add them easier.

    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)
  8. Add more documentation about schema changes

    I made a substantial change to my schema that was not covered in the existing documentation. I resolved the problem based upon the information Ian Ward gave in this thread: https://developer.mongodb.com/community/forums/t/performing-destructive-changes-to-synced-realm/10757/11. This really should be in the documentation.

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

    10 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. Add much more code snippets into docs

    We non-dev users could use much more re-usable code snippets for speeding up our learning curve and creating prototypes.
    I mean like this: https://docs.mongodb.com/realm/triggers/trigger-snippets
    Personally I'd like a usable database trigger which executes an aggregation pipeline.
    I haven't got a working solution neither from in-chat support nor from the community :(

    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. user object documentation

    The documentation for user object (as many other parts) seems incomplete and doesn't provide enough information about the possible responses you can get from the API and the SDK.

    https://docs.mongodb.com/realm/authentication/user-objects

    Please provide documentation for the user object which includes the built-in authentication providers.

    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)
  12. Support for user "Presence"

    At this point in time, it is not possible to determine in Realm Cloud whether a user is connected to a MongoDB Realm app and is online or not. In other words, there is no built in mechanism in Realm for figuring this out. Firebase has had this feature for years, so I think it only nature that Realm should as well. This is absolutely critical for developing something like a chat application.

    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)
  13. Complex Realm Querying (No Partitions)

    So there's currently an issue with Partitions where if you have multiple complex relationships, files that need to be in multiple partitions aren't accessible.

    Let's say you have a User Object and a Tribe Object.
    Each user has a list of tribes they are in, and each tribe has a list of users they are in.

    If you partition for each User, and User 1 and User 2 share a tribe, the User 2 partition will be unable to access the tribe.

    If you partition for Tribes, and Tribe 1 and Tribe 2 that share a User, one partition will…

    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)
  14. disable rules filter

    currently you can only remove filters, why not add a disable option so you can keep them for later? (e.g. testing)

    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)
  15. Prevent App - Cluster Deletion

    We have Realm applications running in Dev, Staging, Production.
    Someone accidentally deleted the Staging application. (It's easy to do it)
    Hopefully, it wasn't a production one.
    Please add a way to lock or prevent Application and Cluster deletion.
    That way, we add an additional step which is a password, for example, and prevent accidents to happen.
    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)
  16. realm-ui

    When creating a free cluster to evaluate realm-ui and sync please warn that 4.4 or higher mongo is required.
    Now i found out when getting started that i have a cluster with 4.2.1 and cannot use the task tracker app sync.

    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)
  17. ObjectId

    We need a way for ids to not have to be unwrapped from $oid before they are assigned as an ObjectId.

    Incoming data:

    {"_id":{"$oid":"..."}}

    Realm class:

    class Item: Object {
    @objc dynamic var _id = ObjectId.generate()
    }

    That's all that should be needed.

    So the default ObjectId class needs:

    enum CodingKeys: String, CodingKey {
    case oid = "$oid"
    }

    then in init(from decoder:Decoder)

    let container = try decoder.container(keyedBy: CodingKeys.self)
    try super.init(string: try container.decode(String.self, forKey: .oid))

    Do that when the .singleValueContainer() call fails.
    That way both use cases are satisfied.

    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)
  18. Copy functions from one cluster to another

    It would be great if you could copy a Realm Service or Function from one cluster to another. I find myself having to open two tabs and coping the function code then checking all settings are the same etc.
    We would normally dev on a "test" cluster then copy Service functions over to "prod" cluster. Or am I missing something?

    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)
  19. Ways to pause a Realm App

    It would be awesome, if there was a way pause a Realm App via functions.

    Currently we are pausing our cluster every night using a trigger. However that causes all our Realm apps' sync and triggers to crash, so I have to manually restart each of them every morning.

    It would be awesome if I could pause/unpause a Realm App from a function. Something like this, maybe:

    context.realm.app([app-id]).pause()
    context.realm.app([app-id]).unpause()

    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)
  20. Decode user token

    Using Realm as an authentication service and a separate backend that then allows the user to connect to separate external APIs, I need to be able to verify that the user is an authenticated user and that their data (only email in this case) match those of the third party external API.

    The request to the third party API runs via admin API channels so it's critical to ensure the user is only able to manipulate their own data (orders, subscriptions etc).

    As far as I've been told there is no way to verify a user that logged into my…

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

Feedback and Knowledge Base